Skip to main content
Glama

check_get

Read-onlyIdempotent

Retrieve service-measured values, fixed criteria, coverage, and current source integrity for a task receipt to verify simulation results and check data provenance.

Instructions

Read service-measured values, fixed criteria, coverage and current source integrity.

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": {
      "task_id": "<task_id>",
      "receipt_id": "<receipt_id>"
    },
    "name": "check_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
receipt_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds only a hint about what is measured (service values, criteria, coverage, source integrity); it says nothing about freshness, failure behavior, or what integrity means in practice. That is modest added value on top of rich annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler, which is good, but it is terse to the point of under-specification rather than efficient. Nothing is front-loaded because there is effectively only one clause.

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 values need not be explained, but the description leaves the two required identifiers undefined and gives no usage context. For a tool sitting among a dozen similarly named check/get siblings, that is not enough for correct invocation.

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?

Both required parameters (task_id, receipt_id) have 0% schema description coverage, so the description carries the full burden — and it says nothing about them. It never indicates that task_id identifies the task and receipt_id anchors the check to a specific submission, nor what formats they take.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Read service-measured values, fixed criteria, coverage and current source integrity" names a verb (read) and lists categories of content, but the resource itself is never identified — an agent cannot tell what a "check" object is or what it belongs to. It is more informative than a tautology yet falls short of a specific verb+resource statement that would distinguish it from siblings like check_run or validation_check.

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, what preconditions must hold (e.g. whether a task must have been run first), or how it differs from the many sibling check/get tools. The agent must infer usage 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.