Skip to main content
Glama

Get the result of a running job

get_job_result
Read-onlyIdempotent

Fetch the result of a slow TinyFish Agent run using its job_id; if status is still running, wait about 15 seconds and call again.

Instructions

Fetch the result of a slow TinyFish Agent run that another Stacks tool started (a job_id from ask_library, a fallback_job_id from an error, or a diagnosis_job_id from health_check). If status is still 'running', wait about 15 seconds and call again.

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": {
      "job_id": "<job_id>"
    },
    "name": "get_job_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job id exactly as returned by another tool.

Output Schema

NameRequiredDescriptionDefault
kindYes
errorYes
job_idYes
resultYesThe Agent's structured result once completed. For kind 'ask': { answer, found, source_urls }.
sourceYesProvenance of the data.
statusYes
agent_stepsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare read-only, idempotent, open-world, non-destructive, so the safety profile is already covered. The description adds genuinely new behavior beyond them: the polling contract and the ~15 second backoff, which is the key operational trait of this tool.

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?

Two sentences, front-loaded with the purpose, then the polling instruction. Every clause carries information; no filler.

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 need not be described, and annotations cover safety. The main residual gap is what happens on terminal non-success states or an invalid/expired job_id, which the description does not address.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the single job_id parameter is already documented as 'exactly as returned by another tool'. The description adds the concrete sources that produce a valid job_id, clarifying provenance beyond the schema text.

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?

States a specific verb and resource ('Fetch the result of a slow TinyFish Agent run') and bounds the input to jobs started by other Stacks tools. The provenance list (ask_library job_id, fallback_job_id, diagnosis_job_id) distinguishes it from those siblings that launch the work.

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

Usage Guidelines5/5

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

Explicitly says this tool is for results of slow runs initiated elsewhere, and that if status is 'running' the caller should wait ~15 seconds and call again. That is both the when-to-use condition and the retry protocol, leaving nothing to inference.

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