Skip to main content
Glama

batch_get

Read-onlyIdempotent

Read batch progress, sample identities, controls, costs, and latest output steps/time to monitor simulations and determine when completed outputs need analysis or checks.

Instructions

Read batch progress, sample identities, controls, costs and latest output steps/time. Missing accounting stays unknown. Computational completion leads to output analysis/checks. Read run_get for full evidence or include_details for all member evidence.

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": "batch_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
batch_idYes
include_detailsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds non-obvious semantics: missing accounting remains "unknown" rather than being backfilled, and computational completion implies the analysis/check stage. These are real data-interpretation cues not present in the annotations.

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?

Purpose is front-loaded in the first clause, and each following sentence carries a distinct fact (unknown accounting, completion semantics, escalation path). The clipped phrasing borders on cryptic in places but wastes no words.

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

Completeness4/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 values needn't be spelled out, and with only two parameters the surface area is small. The description covers scope, escalation, and status interpretation; only the batch_id semantics and the cost of include_details are unaddressed.

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 0%, so the schema only supplies names and a default. The description does add meaning for include_details ("all member evidence"), which is useful, but batch_id is never characterized and the trade-off of enabling details (cost, verbosity) is not stated.

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?

"Read batch progress, sample identities, controls, costs and latest output steps/time" gives a concrete verb plus an enumerated scope of what is returned, which goes well beyond restating the name. It separates itself from run_get by reserving "full evidence" for that sibling, though the telegraphic phrase "sample identities" is left unexplained.

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?

The description explicitly routes the agent: use run_get for full evidence, or set include_details to pull all member evidence. That names an alternative and the condition that selects it. It stops short of saying when this tool should not be used at all (e.g., before a batch exists).

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