Spectrum Data Digital

search_contracts

Search the catalog of organization-only datasets, including daily SAM.gov federal contract opportunities, USAspending and SEC filings. Free, no API key. Returns titles, record counts, price per record and a preview. Use listing_id with the REST catalog endpoint to buy records; this tool searches and previews only.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Results to return, 1-100. Defaults to 20.
`query`	No	One or two words matched against dataset titles. Use exact title wording including punctuation, e.g. "SAM.gov", "contract", "awards", "sanctions", "exclusions".

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses cost ('Free, no API key'), the read-only nature ('searches and previews only'), the scope restriction ('organization-only'), and what a result contains (titles, record counts, price per record, preview). It omits rate limits and pagination behavior beyond the limit parameter.

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?

Three tight sentences: what is searched, what it costs and returns, and where the boundary with purchasing lies. Scope and the preview-only constraint are front-loaded with no filler.

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?

For a two-parameter tool with no annotations and no output schema, the description supplies the auth/cost model, the return fields, and the read-only boundary - enough to call it correctly. Only minor operational details such as pagination behavior are left implicit.

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%, so both limit and query are already documented with examples and constraints, making the baseline 3 appropriate. The description adds no further parameter meaning, and the mention of listing_id refers to an external REST endpoint rather than an argument to this tool, which could momentarily confuse an agent reading parameter 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 - searching a catalog of organization-only datasets - and names concrete content (SAM.gov contract opportunities, USAspending, SEC filings). It also corrects the potentially misleading name by clarifying that the tool 'searches and previews only' rather than returning contracts themselves.

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?

Explicitly draws the boundary between searching/previewing here and buying records via the REST catalog endpoint with listing_id, which is the key usage fork for this tool. It does not address the sibling tools (check_balance, new_uk_companies, screen_company), but those are unrelated enough that no routing guidance is needed.

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

All Spectrum Data Digital tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?