API Monitor MCP

Overview Schema Source Related Servers Discussions Admin

capture_compare

Compare two APMX captures by entry sizes and CRCs to spot inconsistencies. Use it to validate capture integrity or debug API behavior changes.

Instructions

Compare two APMX captures by their stored entry sizes and CRCs.

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": {
      "first_file": "<first_file>",
      "second_file": "<second_file>"
    },
    "name": "capture_compare"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`first_file`	Yes
`second_file`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.26Sep 12, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only what is compared (sizes and CRCs) and says nothing about read-only safety, how large captures are handled, how the 'limit' truncates results, or what a mismatch looks like. For a tool with zero annotation coverage this is a meaningful gap.

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?

A single front-loaded sentence with no filler; the comparison basis is stated immediately. It is efficient, though the terseness is part of why parameter and behavioral details are missing.

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

Completeness2/5

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

An output schema exists, so return-value explanation is not required. However, with no annotations, undocumented parameters, and no statement of prerequisites or the meaning of 'limit', the definition is not complete enough for an agent to call the tool confidently.

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

Parameters2/5

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

Schema description coverage is 0%, with three parameters (first_file, second_file, limit) documented only by their titles. The description implies the two file arguments map to the two captures but adds no detail on path format, and the 'limit' parameter — default 2000 — is left entirely unexplained.

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?

The description states a specific verb (Compare), a specific resource (two APMX captures), and the exact basis of comparison (stored entry sizes and CRCs), which makes the operation concrete. It does not distinguish itself from near-siblings such as capture_compare_calls or capture_validate, so it falls short of a 5.

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?

There is no indication of when to reach for this tool versus capture_info, capture_validate, or capture_compare_calls, and no prerequisites (e.g., both files must be the same capture format) are stated. The agent must infer usage purely from the name and one-line purpose.

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

Deploy Server