Skip to main content
Glama

List the tools of a proxied MCP server

proxy_discover
Read-onlyIdempotent

Discover which tools a proxied MCP server exposes, or list all proxied servers when no server is specified, to identify callable tools.

Instructions

List the tools exposed by an external MCP server that this server proxies, or list the proxied servers themselves when no server is named. Not covered by proxy_call, which invokes a tool rather than listing them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxy_discover"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverNoServer name. Every proxied server when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered; the description adds the dual-mode dispatch rule and the boundary against proxy_call. It does not describe error behavior for unknown server names or any auth/connectivity requirements for reaching an external server, which would be useful for an openWorld tool.

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?

Two sentences, no waste, with the primary behavior front-loaded and the disambiguation second. The compact framing matches the tool's single-parameter simplicity.

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?

No output schema exists, and the description does implicitly signal the two possible return shapes (tool list vs. server list), which is enough for an agent to act. Minor gaps remain around failure handling for an unreachable or unnamed external server, but nothing essential is missing for correct invocation.

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?

With one fully-documented parameter, the schema baseline is 3; the description earns more by making explicit that omitting `server` changes the result from a tool list to a server list, which the schema only implies with 'Every proxied server when omitted'. That is a meaningful behavioral consequence rather than a restatement.

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?

Names a specific verb (list) and resource (tools of a proxied MCP server), and explicitly states the second mode: listing the proxied servers themselves when no server is named. It also names proxy_call as the contrasting tool, so an agent can distinguish the two without opening either 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?

Explicitly states the discriminating condition against proxy_call (invokes a tool rather than listing them) and the no-argument case that switches behavior to server enumeration. It stops short of covering failure modes, such as what to do with an unknown server name, but the when-to-use guidance is clear.

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