Skip to main content
Glama
nikolai-vysotskyi

trace-mcp

by nikolai-vysotskyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

batch

Read-onlyIdempotent

Run several tool calls in a single MCP request to cut down round-trips. Group independent queries like get_outline and search together for faster results.

Instructions

Execute multiple trace-mcp tools in a single MCP request. Dispatches any registered tool by name, including tools this session's preset defers — so a deferred tool is callable here without a load_tools round-trip (tools.exclude stays a hard restriction). Use to reduce round-trips when you need several independent queries (e.g., get_outline for 3 files, or search + get_symbol together). Read-only (delegates to other tools). Returns JSON: { batch_results: [{ tool, result }], total }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
callsYesArray of tool calls to execute (max 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.3.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Addedv1.41.0
  3. Removedv1.38.0
  4. Changed3 schema fields changedv1.35.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / calls / items / additionalProperties
      Removed value: -false
    • addedInput schema / properties / calls / items / properties / args / propertyNames
      Added value: +{
+  "type": "string"
+}
  5. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description explains that the tool delegates to other tools, can invoke deferred tools without load_tools, enforces tools.exclude as a hard restriction, and documents the JSON return shape. This adds meaningful behavioral context not present in 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 dense sentences cover purpose, use case, restrictions, read-only behavior, and return shape. Every sentence earns its place and key information is front-loaded.

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

Completeness5/5

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

Despite having no output schema, the description provides the return format. The schema covers parameter validation, annotations cover safety, and the description covers usage, restrictions, and batching intent. Nothing essential for an agent to call this correctly is missing.

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?

The input schema already fully documents the 'calls' parameter with item schemas and min/max constraints, so the baseline is 3. The description adds value with concrete usage examples and clarifies that deferred tool names are acceptable, going slightly beyond schema-only information.

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?

Description states a specific verb ('Execute multiple trace-mcp tools in a single MCP request') and distinguishes itself from siblings by enabling batched dispatch, including deferred tools. It is immediately clear what this tool does and how it differs from individual tools like get_outline or search.

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?

Explicitly says 'Use to reduce round-trips when you need several independent queries,' gives concrete examples, and clarifies when a tool is still not callable ('tools.exclude stays a hard restriction'). This gives clear when-to-use and when-not-to-use guidance.

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

Deploy Server

Other Tools