mcp-broker

Overview Schema Source Related Servers Discussions Admin

broker_describe_tool

Inspect an upstream MCP tool's description, input schema, and metadata using its broker-qualified name before calling it, eliminating guesswork.

Instructions

Describe one profile-visible upstream MCP tool by broker-qualified name. Use this after broker_search_tools and before broker_call_tool so the client can inspect the exact description, input schema, upstream owner, transport, and mutating metadata instead of guessing arguments.

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": {
      "name": "<name>"
    },
    "name": "broker_describe_tool"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Full broker-qualified tool name to inspect, such as an upstream prefix joined to the upstream tool name by the configured namespace separator.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.1.2May 28, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / description

Added value: +"Describe request for one catalog entry. The name must be the full broker-qualified tool name returned by broker_search_tools or another catalog response, including the upstream prefix and namespace separator."

addedInput schema / properties / name / description

Added value: +"Full broker-qualified tool name to inspect, such as an upstream prefix joined to the upstream tool name by the configured namespace separator."

addedInput schema / properties / name / examples

Added value: +[
+  "github.get_me",
+  "filesystem.read_file"
+]

addedInput schema / properties / name / minLength
```
Added value: +1
```

First observedv1.1.1May 28, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It mentions the tool returns 'exact description, input schema, upstream owner, transport, and mutating metadata,' which is transparent about the output. However, it does not discuss error handling, permissions, or rate limits, leaving some gaps for a bare description.

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 concise sentences: the first states the action, the second provides workflow context. Every word is purposeful with no redundancy, making it highly efficient and easy to parse.

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?

Given the tool's simplicity (one parameter, no output schema) and the presence of sibling tools, the description is fairly complete. It explains the workflow position and return contents, though it could mention error cases or that the name must come from search results.

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

Parameters3/5

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

Parameter schema coverage is 100% with a thorough description and examples. The tool description adds 'by broker-qualified name' but largely restates schema info, so it provides minimal additional value beyond the schema.

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?

The description clearly states the tool's purpose: 'Describe one profile-visible upstream MCP tool by broker-qualified name.' It also distinguishes from siblings by specifying its place in the workflow, making the purpose highly specific and unambiguous.

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

Usage Guidelines5/5

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

The description explicitly advises when to use this tool: 'Use this after broker_search_tools and before broker_call_tool.' It also explains the benefit—avoiding guesswork—which helps the agent decide correctly among siblings.

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

Deploy Server