Choosing and describing tools

Tools are what your AI sees and can call. Choosing and describing them well noticeably improves the answers.

Enable or disable a tool

In the "Tools" tab, use the "Enabled" column to choose what the AI can call, then click "Save". Until you save, the "Unsaved changes" message is shown; "Discard" drops your changes. The "Search tools" box helps filter long lists. A disabled tool is not visible to the AI.

Active tool limit

The number of tools that can be active per server is set by your plan (the "N / limit active" counter is at the top of the tab). On import, the first tools in the spec order are enabled and the following ones are disabled, with the TOOLS_DISABLED_OVER_LIMIT warning. Enabling a tool beyond the limit is refused (PLAN_LIMIT_REACHED): disable another one first. See Quotas and plans.

Rename a tool

Click "Edit" on the tool's row, change the "Name" field, then "Apply" and "Save". Rules:

• letters, digits, _ and - only, 64 characters at most;
• the name is unique within the server, case-insensitively;
• search_documents and read_document are reserved.

A customized tool shows "Modified".

Rewrite the description

The description is what the AI reads to decide whether to call the tool. It is generated from the operation's summary, then description, otherwise from METHOD /path. You can rewrite it (1,000 characters maximum). "Restore generated value" goes back to the text from the spec. Your changes survive a spec update.

Tool types

The "Type" column classifies each tool:

These hints are passed to the AI (MCP annotations readOnlyHint and destructiveHint): write and delete tools are flagged as changing data, which encourages clients to ask for confirmation. Disable the write or delete tools your AI does not need.

Document tools

When the server holds documents, the search_documents and read_document tools are added automatically ("Always on"). They do not count toward the limit of 50. See Documents and search.

Best practices

• Name with a verb and an object: list_orders, create_invoice.
• Say when to use the tool, and when not to.
• Specify the units and formats of parameters ("amount in cents", "date as YYYY-MM-DD").
• Keep few tools active: an AI chooses better among ten clear tools than among fifty.

Example

The generated operation is called get_orders_id, with the description GET /orders/{id}. You rename it get_order and describe it like this:

Reads an order by its identifier (id parameter, text). Use when the user
gives an order number. Returns the status and the order lines.

After "Apply" then "Save", the AI sees get_order with this text.