Skip to main content
Glama

Estimate a research job

spur_estimate_data_job
Read-onlyIdempotent

Get the credit estimate without creating, running, saving, or charging a recipe job. Execution is a separate call to spur_run_data_job and starts immediately.

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": {
      "recipe_key": "<recipe_key>",
      "params": "<params>"
    },
    "name": "spur_estimate_data_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes
recipe_keyYes
selectionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description usefully adds that no job is created, saved, or charged, and that execution starts immediately once run is called, but says nothing about what the estimate contains or whether it is a snapshot in time.

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 tight sentences with no filler; the non-side-effect guarantee is front-loaded ahead of the execution routing note.

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

Completeness2/5

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

For a tool with a nested selections schema, 0% parameter coverage, and no output schema, the description never says what the estimate returns or how selections affect pricing. It covers the safety story but leaves the calling contract thin.

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 description coverage is 0% across three parameters, including a nested selections object with mode/fallbackPolicy enums, and the description supplies no meaning for recipe_key, params, or selections. An agent must infer parameter intent entirely from names.

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 (get the credit estimate) and explicitly scopes it as not creating, running, saving, or charging a job, which cleanly separates it from spur_run_data_job.

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?

Implies the preview-before-execution workflow and names spur_run_data_job as the execution alternative, warning that the run starts immediately. It stops short of an explicit 'call this first when...' instruction, but the routing context is clear.

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