api-flow-analyzer

track_call

Record and track an individual API call with metadata

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": {
      "method": "<method>",
      "endpoint": "<endpoint>",
      "duration_ms": "<duration_ms>",
      "status_code": "<status_code>"
    },
    "name": "track_call"
  }
}

Input Schema

Name	Required	Description
`method`	Yes	HTTP method (GET, POST, etc.)
`endpoint`	Yes	API endpoint URL
`duration_ms`	Yes	Call duration in milliseconds
`status_code`	Yes	HTTP status code
`service_name`	No	Source service identifier
`response_size_bytes`	No	Response payload size

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 16, 2026

TDQS

B3/5.0

Behavior2/5

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

With no annotations available, the description carries the full burden of behavioral disclosure. It only hints at a write/recording operation but does not explain side effects, persistence, authentication, or return values. This is insufficient for an agent to predict the tool's impact.

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

Conciseness4/5

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

The description is a single, direct sentence with no filler. However, it is under-specified, which detracts from its structure since it omits valuable context; for a tool with 6 parameters, a slightly more detailed description would be appropriate.

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

Completeness1/5

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

There is no output schema and no annotations, yet the tool has six parameters. The description is extremely brief and does not explain return values, the relationship to siblings, or any behavioral nuances. This leaves the tool largely underdocumented.

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?

The schema provides complete descriptions for all six parameters, so the baseline is 3. The description's mention of 'metadata' adds no specific meaning beyond the schema, so no additional credit is warranted.

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 records and tracks an individual API call with metadata, using specific verbs and a clear resource. This distinguishes it from the sibling analysis tools (analyze_flow, calculate_savings, etc.) which operate on flows or multiple calls.

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?

No guidance is provided on when to use this tool versus the sibling tools. The description does not mention any preconditions, alternatives, or exclusions, leaving the agent to infer usage from purpose alone.

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

All api-flow-analyzer tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.