Skip to content

Commit 0f7008c

Browse files
chore(internal): grammar fix (it's -> its)
1 parent 3a1120e commit 0f7008c

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

packages/mcp-server/src/code-tool.ts

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ import { WorkerInput, WorkerError, WorkerSuccess } from './code-tool-types';
1212
/**
1313
* A tool that runs code against a copy of the SDK.
1414
*
15-
* Instead of exposing every endpoint as it's own tool, which uses up too many tokens for LLMs to use at once,
15+
* Instead of exposing every endpoint as its own tool, which uses up too many tokens for LLMs to use at once,
1616
* we expose a single tool that can be used to search for endpoints by name, resource, operation, or tag, and then
1717
* a generic endpoint that can be used to invoke any endpoint with the provided arguments.
1818
*
@@ -23,7 +23,7 @@ export async function codeTool(): Promise<Endpoint> {
2323
const tool: Tool = {
2424
name: 'execute',
2525
description:
26-
'Runs Typescript code to interact with the API.\nYou are a skilled programmer writing code to interface with the service.\nDefine an async function named "run" that takes a single parameter of an initialized client, and it will be run.\nDo not initialize a client, but instead use the client that you are given as a parameter.\nYou will be returned anything that your function returns, plus the results of any console.log statements.\nIf any code triggers an error, the tool will return an error response, so you do not need to add error handling unless you want to output something more helpful than the raw error.\nIt is not necessary to add comments to code, unless by adding those comments you believe that you can generate better code.\nThis code will run in a container, and you will not be able to use fetch or otherwise interact with the network calls other than through the client you are given.\nAny variables you define won\'t live between successive uses of this call, so make sure to return or log any data you might need later.',
26+
'Runs TypeScript code to interact with the API.\nYou are a skilled programmer writing code to interface with the service.\nDefine an async function named "run" that takes a single parameter of an initialized client, and it will be run.\nDo not initialize a client, but instead use the client that you are given as a parameter.\nYou will be returned anything that your function returns, plus the results of any console.log statements.\nIf any code triggers an error, the tool will return an error response, so you do not need to add error handling unless you want to output something more helpful than the raw error.\nIt is not necessary to add comments to code, unless by adding those comments you believe that you can generate better code.\nThis code will run in a container, and you will not be able to use fetch or otherwise interact with the network calls other than through the client you are given.\nAny variables you define won\'t live between successive uses of this call, so make sure to return or log any data you might need later.',
2727
inputSchema: { type: 'object', properties: { code: { type: 'string' } } },
2828
};
2929

packages/mcp-server/src/dynamic-tools.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ function zodToInputSchema(schema: z.ZodSchema) {
1414
/**
1515
* A list of tools that expose all the endpoints in the API dynamically.
1616
*
17-
* Instead of exposing every endpoint as it's own tool, which uses up too many tokens for LLMs to use at once,
17+
* Instead of exposing every endpoint as its own tool, which uses up too many tokens for LLMs to use at once,
1818
* we expose a single tool that can be used to search for endpoints by name, resource, operation, or tag, and then
1919
* a generic endpoint that can be used to invoke any endpoint with the provided arguments.
2020
*

0 commit comments

Comments
 (0)