Skip to main content
Glama

Register a run

futility_register_run

Register a run with its alternatives and operator-registered source identities (strings or {id, aliases}) before judging.

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": {
      "run_id": "<run_id>"
    },
    "name": "futility_register_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
sourcesNo
alternativesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish this is a non-read-only, non-destructive mutation, and the description adds that source identities are operator-registered rather than inferred. It does not say whether registering the same run_id overwrites prior state, whether validation occurs, or what the call returns, which matters for a mutation with no output schema.

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?

A single sentence with the action front-loaded and no filler. The parenthetical shape hint is well placed, though the sentence packs three ideas and reads slightly awkwardly.

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 three-parameter mutation with no output schema and zero schema descriptions, the definition covers the hardest gap (the source identity format) but leaves the identifier and alternatives semantics and any post-call state expectations unaddressed. It is adequate, not complete.

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 description must compensate. It does add real meaning for `sources` by stating they are strings or {id, aliases} objects, which the bare `array` schema omits. However, `run_id` is unexplained and `alternatives` is merely restated by name, leaving two of three parameters thin.

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 gives a specific verb and resource ("Register a run") and enumerates the payload it carries: alternatives and operator-registered source identities. The trailing "before judging" signals its position relative to the futility_judge sibling, though it never names that tool 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?

The phrase "before judging" implies a prerequisite ordering: register first, then judge. That is useful implied usage guidance, but there is no explicit statement of when to skip this tool, whether re-registration is allowed, or which sibling to reach for next among receipt, verdict, or waste_report.

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