Skip to main content
Glama

get_analyst_job

Read-only

Check the status and result of an ask_analyst job by job_id. Get the finished brief, structured summary, and quality flags after processing completes.

Instructions

Fetch the status and result of an ask_analyst run by job_id. Job status is ONLY "processing" (still running — poll again in ~10-20s), "done" (with the finished brief and meta.tokens), or "error". When done, result_quality.status ("complete" | "partial", with any issues[]) reports whether the structured output is fully populated — this is SEPARATE from the job status (a done job can carry a partial result). Free of token charges — the run itself is charged once on completion. A job is visible only to the API key owner that created it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYesThe job_id returned by ask_analyst.
response_formatNo"full" (default) returns the prose brief alongside the structured result. "compact" omits the prose brief and returns only the structured result — which still carries the assembled structured_summary — so a re-fetch costs materially fewer context tokens.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaNoQuery echo, token charge/balance (meta.tokens), and pagination where applicable.
briefNo
errorNoFailure reason when status is "error".
job_idNo
statusNo"processing" | "done" | "error".
messageNo
progressNoPipeline progress while the job is processing. completed_steps reaches total_steps ONLY when status is "done".
created_atNo
updated_atNo
Behavior5/5

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

Annotations declare readOnlyHint=true, and the description aligns with that, adding rich behavioral detail: exact statuses, processing intervals, separation of result_quality from job status, token charging behavior, and owner-only visibility. These go well beyond structured annotations.

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?

Five dense sentences cover statuses, polling, quality caveat, and access constraints with no filler. Information is front-loaded with the core action first.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a polling endpoint with output schema, the description covers all needed operational context: status meanings, polling behavior, quality distinction, and access control. The response_format parameter is already documented in the schema, so no gap.

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%, with both job_id and response_format documented. The description adds little beyond the schema (e.g., that job_id comes from ask_analyst), so parameter semantics are adequately handled by the schema itself.

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?

The description names a specific verb ('Fetch') and a clear resource ('status and result of an ask_analyst run by job_id'), which distinguishes it from sibling tools like ask_analyst that create runs. It fully clarifies what the tool does.

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?

Clear context is given for polling ('poll again in ~10-20s') and it implicitly identifies this as the retrieval counterpart to ask_analyst. It doesn't explicitly name alternative tools, but the wording and sibling set make the usage context obvious, though no explicit when-not-to-use list is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Off-Nadir-Lab/offnadir-delta-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server