Skip to main content
Glama

List research jobs

spur_list_data_jobs
Read-onlyIdempotent

Recover job IDs, statuses and budgets, including jobs started in the app. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "spur_list_data_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of items to return
offsetNoNumber of items to skip, for pagination
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two genuinely new behavioral facts beyond the annotations: the listing includes jobs created outside the API ('started in the app'), and the call incurs no cost ('Free'). It does not mention pagination behavior or result caps, which would have completed the picture.

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?

Two short sentences, front-loaded with the returned fields and followed by scope and cost notes; there is no filler. The fragment 'Free.' is terse but earns its place by conveying billing behavior, though 'Recover' is a slightly unusual verb choice for a list operation.

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?

There is no output schema, so the description reasonably carries the return-shape burden by naming job IDs, statuses and budgets, and it discloses the no-cost trait. However, for a paginated list tool it omits pagination semantics, result limits, and any explanation of the status filter, leaving meaningful gaps for an agent planning a full enumeration.

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

Parameters2/5

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

Schema coverage is only 67%: limit and offset are documented in the schema, but the status parameter has no description, no enum, and only a maxLength constraint. The description never mentions filtering by status or what values are accepted, so it does not compensate for the uncovered parameter. With the schema doing partial work and the description adding nothing about filtering, this falls below the baseline of 3.

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 states a specific retrieval action on a specific resource and enumerates the fields returned ('job IDs, statuses and budgets'), which is more than a restatement of the title. It also scopes coverage with 'including jobs started in the app.' It stops short of distinguishing itself from siblings such as spur_get_data_job or spur_control_data_job, so it is clear but not sibling-differentiated.

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 can infer this is the discovery call for finding job IDs and their status/budget before acting on a specific job. No alternative is named and there is no explicit when-not guidance (e.g., use spur_get_data_job when you already have an ID). The 'Free' note hints at cost considerations but is not framed as selection criteria.

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