stormgtm-mcp

Batch status

batch_status

Track progress and results for a lead qualification batch, including verdict, score, and reasons per lead.

Instructions

Progress and results for a batch. Results include verdict, score, and reasons per lead.

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

Input Schema

Name	Required	Description	Default
`id`	Yes
`limit`	No
`offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 3, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses the result shape (verdict, score, reasons per lead), which is genuinely useful, but says nothing about read-only safety, rate limits on polling, pagination behavior, or what 'progress' means for an in-flight batch.

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?

Two short sentences with no filler, and the payload contents are stated up front. Efficient, though the brevity borders on under-specification rather than true conciseness.

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?

There is no output schema, so the description must describe returns; it partially does by naming verdict, score, and reasons per lead. It omits polling/terminal-state semantics and pagination behavior for limit and offset, leaving an agent without enough to call it confidently in all cases.

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% and the description never mentions id, limit, or offset. The required id and the paging controls are left entirely to infer from bare types and constraints, so the description fails to compensate for the coverage gap.

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 the resource (a batch) and what is returned (progress and results), which is a clear, specific read purpose. However, it does not differentiate itself from the sibling check_batch, so an agent cannot tell from the description alone which of the two to call.

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 guidance on when to use this tool versus check_batch, no indication of polling cadence, and no stated prerequisite such as needing a batch id from an earlier submission. Usage must be inferred entirely from the name.

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