Skip to main content
Glama

Get a Data Search job

spur_get_data_job
Read-onlyIdempotent

Status, counts, and results of a Data Search job. Results are available while the job runs. Each value names its provider. Free.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of items to return
stateNopassed = matched
job_idYes
offsetNoNumber of items to skip, for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for adding non-structural facts: partial results are readable mid-run, result values carry their provider, and the call is free. It stops short of describing pagination behavior or how job completion is signaled.

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?

Four short sentences, front-loaded with what is returned, then the key mid-run caveat, then the provider and cost notes. No filler and nothing buried.

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 indicating the return shape, and it does so (status, counts, results, provider-named values). Missing is any note on how to tell a job has finished or how pagination relates to the reported counts, which matters for a job-polling tool.

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 coverage is 75% and the enum semantics for 'state' are already documented in the schema ('passed = matched'). The description adds nothing about job_id format or how limit/offset interact with the counts reported, so it stays at the baseline where the schema does the heavy lifting.

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 names the resource (a Data Search job) and what it returns (status, counts, results), which lets an agent distinguish it from siblings like spur_run_data_job or spur_control_data_job. It does not explicitly contrast itself with spur_list_data_jobs (single job vs. list), so differentiation is inferred rather than stated.

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?

'Results are available while the job runs' implies polling usage, which is useful implicit guidance. However, there is no explicit statement of when to call this vs. checking spur_list_data_jobs or when the job should instead be driven via spur_control_data_job, and no prerequisites are given.

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