Skip to main content
Glama

Get batch results

get_batch_items
Read-only

List a batch's per-address results: each address with its verification status, recommended action and signals. Free and read-only. Page through with limit and offset, and filter by item status. Check get_batch_status first so you read a completed batch.

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": {
      "batch_id": "<batch_id>"
    },
    "name": "get_batch_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1 to 1000. Defaults to 100.
offsetNoHow many items to skip, for paging. Defaults to 0.
statusNoOnly return items in this state. Omit to return all items.
batch_idYesThe batch_id returned by create_verify_batch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the description needs to add only what they do not cover. It does that by disclosing that calls are free and by previewing the return payload, though it omits details like whether paging is stable or how large batches behave.

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?

Three short sentences, each earning its place: return shape first, cost/safety second, operational mechanics third. Nothing is repeated or padded.

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

Completeness5/5

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

With no output schema, the description carries the return-value explanation and does so by naming the per-address fields. It also covers cost, read-only safety, paging and the prerequisite batch-status check, leaving no material gap for correct invocation.

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 limit, offset, status and batch_id are already fully documented. The description merely restates the paging and status-filtering intent without adding format, bounds or interaction details beyond the schema, which is the expected baseline.

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 opens with a specific verb and resource ('List a batch's per-address results') and enumerates the returned fields (verification status, recommended action, signals). This clearly separates it from get_batch_status, which the description positions as a separate status-check step.

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

Usage Guidelines4/5

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

It gives a concrete prerequisite ('Check get_batch_status first so you read a completed batch') and explains paging/filtering usage. It stops short of stating when this tool should not be used, but the sequencing guidance is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources