Skip to main content
Glama

sp_batch_check_status

Read-only

Checks the status of up to 10 normative document references independently, preserving each input ID and continuing after per-item errors.

Instructions

Check 1..10 references independently. Each item: input_id, code, optional snapshot_id. Errors preserve input_id and do not abort other items. No automatic project applicability.

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": {
      "items": "<items>"
    },
    "name": "sp_batch_check_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNo
itemsYes
refreshNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, non-destructive. On top of that, the description discloses genuinely useful behavior: the 1..10 item cap, per-item error isolation that preserves input_id and does not abort remaining items, and the caveat that no automatic project applicability is applied. It stops short of describing return values or what a status result contains.

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?

Four short sentences, front-loaded with the batch scope and the item structure, then error semantics and a scope caveat. Telegraphic phrasing but no wasted words.

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 tool with zero schema descriptions and no output schema, key gaps remain: the meaning of as_of and refresh, and what a check result contains. The item contract and error behavior are covered, but the surrounding parameters are not.

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 coverage is 0%, so the description must compensate. It does document the item shape (input_id, code, optional snapshot_id), which is valuable because the schema types items as an unconstrained object array. However, neither as_of nor refresh is explained anywhere, leaving two of three top-level parameters undocumented.

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 operation: checking up to 10 references independently, one by one. It makes clear this is the batch variant and hints at what an item consists of. It doesn't explicitly name the single-item sibling sp_check_status, so differentiation is implied but not stated.

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

Usage Guidelines3/5

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

The '1..10 references' bound implies this is used for multiple items at once, which implicitly points single checks elsewhere. But there is no explicit when-to-use vs sp_check_status, and no stated prerequisites for the referenced codes.

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