Skip to main content
Glama

One run and its receipt

get_run
Read-only

One Federated Computing run in detail: what it showed, the model and data, hardware, location, result, payment, and whether its receipt verifies (checked now, with the same code as the receipt checker).

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

Input Schema

NameRequiredDescriptionDefault
idYesThe run id, from list_runs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / enum
      Previous value: -[
      -  "sealed-tdx-gpu",
      -  "sealed-tdx",
      -  "gpu-llm-14b",
      -  "gpu-llm-7b",
      -  "gpu-llm",
      -  "pytorch-model",
      -  "gpu-llm-free",
      -  "gpu-llm-graded",
      -  "gpu-llm-quant",
      -  "join-across-banks",
      -  "federated-round",
      -  "pilot-rehearsal",
      -  "gpu-compute",
      -  "three-banks",
      -  "governed",
      -  "intel-tdx",
      -  "first-run"
      -]New value: +[
      +  "sealed-tdx-gpu",
      +  "sealed-tdx",
      +  "gpu-llm-72b",
      +  "gpu-llm-14b",
      +  "gpu-llm-7b",
      +  "gpu-llm",
      +  "pytorch-model",
      +  "gpu-llm-free",
      +  "gpu-llm-graded",
      +  "gpu-llm-quant",
      +  "join-across-banks",
      +  "federated-round",
      +  "pilot-rehearsal",
      +  "gpu-compute",
      +  "three-banks",
      +  "governed",
      +  "intel-tdx",
      +  "first-run"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / id / enum
      Previous value: -[
      -  "sealed-tdx-gpu",
      -  "sealed-tdx",
      -  "gpu-llm-14b",
      -  "gpu-llm-7b",
      -  "gpu-llm",
      -  "pytorch-model",
      -  "gpu-llm-free",
      -  "gpu-llm-graded",
      -  "join-across-banks",
      -  "federated-round",
      -  "pilot-rehearsal",
      -  "gpu-compute",
      -  "three-banks",
      -  "governed",
      -  "intel-tdx",
      -  "first-run"
      -]New value: +[
      +  "sealed-tdx-gpu",
      +  "sealed-tdx",
      +  "gpu-llm-14b",
      +  "gpu-llm-7b",
      +  "gpu-llm",
      +  "pytorch-model",
      +  "gpu-llm-free",
      +  "gpu-llm-graded",
      +  "gpu-llm-quant",
      +  "join-across-banks",
      +  "federated-round",
      +  "pilot-rehearsal",
      +  "gpu-compute",
      +  "three-banks",
      +  "governed",
      +  "intel-tdx",
      +  "first-run"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / id / enum
      Previous value: -[
      -  "sealed-tdx-gpu",
      -  "sealed-tdx",
      -  "gpu-llm-14b",
      -  "gpu-llm-7b",
      -  "gpu-llm",
      -  "join-across-banks",
      -  "federated-round",
      -  "pilot-rehearsal",
      -  "gpu-compute",
      -  "three-banks",
      -  "governed",
      -  "intel-tdx",
      -  "first-run"
      -]New value: +[
      +  "sealed-tdx-gpu",
      +  "sealed-tdx",
      +  "gpu-llm-14b",
      +  "gpu-llm-7b",
      +  "gpu-llm",
      +  "pytorch-model",
      +  "gpu-llm-free",
      +  "gpu-llm-graded",
      +  "join-across-banks",
      +  "federated-round",
      +  "pilot-rehearsal",
      +  "gpu-compute",
      +  "three-banks",
      +  "governed",
      +  "intel-tdx",
      +  "first-run"
      +]
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, closed-world). The description adds real behavioral context beyond them: the receipt is verified live at call time ('checked now, with the same code as the receipt checker'), telling the agent the response reflects fresh computation rather than a stored flag. It stops short of noting cost, latency, or what a failed verification looks like.

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?

One long but front-loaded sentence; the head 'One Federated Computing run in detail' lands before the field enumeration, and each listed item earns its place because there is no output schema to describe the return shape.

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?

With no output schema, the description carries the burden of describing return content and does so thoroughly. It is a simple one-param read-only tool, so the remaining gap is only routing guidance, not missing call-critical information.

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% and the single `id` parameter is documented with its source (list_runs) plus a closed enum of valid ids. The description adds nothing about the parameter, so baseline 3 is appropriate.

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 a specific verb+resource: fetch one Federated Computing run 'in detail', and enumerates what that detail spans (model, data, hardware, location, result, payment, receipt verification). The 'one' framing implicitly contrasts with the list_runs sibling that supplies ids, though it doesn't name it outright.

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?

Usage is only implied: an agent infers this is the drill-down after list_runs, reinforced by the schema note 'The run id, from list_runs'. There is no explicit when-to-use/when-not statement, no mention of alternatives such as get_overview or estimate_cost for aggregate or cost-only questions.

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