Skip to main content
Glama
Sign In
syncause-debug-mcp

syncause-debug-mcp

by Syncause
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

inspect_method_snapshot

Inspect a specific method execution for a request to retrieve input/output parameters, local variables, and scoped logs, optionally including sub-method summaries and key IO.

Instructions

Deep dive into a specific method for a given request, returning precise input/output parameters, local variables, and logs generated within its scope.

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": {
      "projectId": "<projectId>",
      "traceId": "<traceId>",
      "className": "<className>",
      "methodName": "<methodName>"
    },
    "name": "inspect_method_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
traceIdYesUnique identifier.
classNameYesFull class name of the method.
projectIdYesThe unique identifier of the project.
methodNameYesName of the method.
includeSubCallsNoWhether to include execution summaries and key IO of sub-methods.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.15

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It usefully describes the returned data, which matters because there is no output schema, but it does not explicitly state that the operation is read-only, whether logs may be truncated or sensitive, or any access constraints.

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?

A single sentence with zero waste, front-loaded with the tool's core action and then listing the returned artifacts. Every phrase contributes to understanding what the tool does.

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

Completeness3/5

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

For a five-parameter tool with no annotations and no output schema, the description explains the return contents but omits when to choose it over siblings and any read-only or security context. It is minimally complete but has clear gaps for an agent selecting and invoking it confidently.

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?

Schema description coverage is 100%, so the schema already documents each parameter; baseline 3 applies. The description's 'specific method for a given request' loosely maps to traceId/className/methodName but adds no detail on includeSubCalls or projectId beyond what the schema provides.

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

Purpose4/5

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

States a specific verb ('Deep dive') and resource ('specific method for a given request'), and enumerates what it returns: input/output parameters, local variables, and logs. It does not explicitly distinguish itself from sibling get_trace_insight, but an agent can infer that it drills into one method rather than providing a broad trace view.

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

Usage Guidelines2/5

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

Provides no explicit when-to-use guidance, no mention of alternatives such as get_trace_insight or search_debug_traces, and no preconditions. The phrase 'for a given request' gives context but not selection criteria, leaving the agent to infer usage from the name alone.

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