Skip to main content
Glama

list_mcp_tools

Read-onlyIdempotent

List tools available from a connected outbound MCP server. Requires serverId from list_mcp_servers. Use when discovering what that connector can do.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serverId": "<serverId>"
    },
    "name": "list_mcp_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdYesMCP server ID

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the meaningful constraint that the server must already be connected and that the ID comes from list_mcp_servers, but says nothing about behavior on an unknown/disconnected serverId, whether results are cached, or the shape of the returned tool entries. Modest value on top of annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: what it does, what it needs, when to use it. The scope statement is front-loaded and no sentence is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only listing tool, the description covers purpose, prerequisite, and trigger. Since no output schema exists, the lack of any hint about what each listed tool entry contains is a minor residual gap, but nothing that would cause a misinvocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is documented as 'MCP server ID', so the baseline is already met. The description goes beyond it by naming where the value must come from (list_mcp_servers), which prevents the common error of passing a raw or arbitrary ID.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List tools') plus the scope qualifier 'from a connected outbound MCP server', which distinguishes it from list_mcp_servers (servers, not tools) and the generic list_tools. An agent can tell what is being enumerated and over which object without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use when discovering what that connector can do' gives a clear usage trigger, and 'Requires serverId from list_mcp_servers' supplies the prerequisite and source of the value. It stops short of an explicit when-not or a named alternative (e.g., the sibling list_tools), so it is clear context rather than full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources