Skip to main content
Glama

Save Data Search results

spur_save_data_results

Save Data Search results (from spur_data_search) or a job's matched items (from spur_run_data_job) as the user's properties, with owners that outreach can use. Free: the search already paid for the data. Unknown job items can go to a separate list for review.

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_save_data_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNo
list_idNoProperty list for the saved properties
resultsNo
entity_idsNoJob only: save selected result entities
include_unknownNoJob only: also save unknown items
unknown_list_idNoJob only: list for unknown items

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent, closed-world write. Beyond that, the description adds two genuinely useful behavioral facts not in the annotations: saving is free because the search already paid for the data (relevant given the credit-related siblings), and unknown job items can be diverted to a separate list. It does not disclose batching limits or what happens on repeat saves.

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?

Three short sentences, front-loaded with the action and sources, then cost, then the unknown-item branch. The telegraphic phrasing ('Free: the search already paid for the data') is dense but not wasteful.

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?

No output schema exists, so the description should say what is returned or how many properties are created, and it does not. It also leaves the valid parameter combinations ambiguous (all 6 parameters are optional) and omits the 100-result / 5000-entity caps. Adequate to pick the tool, thin for calling it correctly.

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?

With 67% schema coverage across 6 optional parameters, the description adds real meaning by separating the two calling modes (results for search, job_id/entity_ids for a job) and explaining the unknown_list_id/review-list concept that the schema only labels tersely. It leaves list_id and the results payload shape to the schema.

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 a specific verb (save) and two precise resources (results from spur_data_search, matched items from spur_run_data_job) and states the outcome: they become the user's properties. It distinguishes the two input sources clearly, but does not differentiate itself from sibling save tools such as spur_save_properties or spur_add_properties_to_list.

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?

It states the trigger conditions explicitly: use after a data search or after running a data job, and it notes that unknown job items can be routed to a separate review list. It gives no explicit when-not guidance or comparison to other save/add-properties tools, so it stops short of full routing guidance.

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