Skip to main content
Glama

Find candidate data series

find_data
Read-onlyIdempotent

Returns up to 10 data series that might answer a data question, each labelled with the publisher's title, place (code and level), unit, frequency, latest value, range, source and licence, and the call_api arguments that return exactly that series. Never returns a value on its own guess: status is "candidates" or "none" (with a reason). A candidate with related_only ("needs_place": no place named; "no_place": the series has no place, the question names one; "other_measure": it measures something else than asked) has no call_api arguments: it is related, not the asked series. A none with reason "needs_place" may carry calls: call_api arguments of the asked measure with {place} left open, to fill in with the place the user means. When to use: for a data question, pass query or the parts measure, place and period; then choose a candidate whose measure, place and time match the question and pass its call_api arguments to call_api. If none matches, tell the user this service does not have it. Read-only, no API key or signup. Free quota: 1000 calls/day per IP, shared across tools.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of candidates, 1-10 (default 10)
placeNoPlace name or code, e.g. "California" or "US-CA"
queryNoThe question in plain text, max 500 characters
periodNoAsked time, e.g. "2023" or "2026-09"
measureNoWhat is measured, e.g. "unemployment rate" (with place and period: used instead of query)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say read-only, idempotent, open-world, non-destructive; the description adds substantial behavior beyond them: the 'candidates'/'none' status contract, the four related_only reasons and why they carry no call_api arguments, the open {place} placeholder convention, and the 1000 calls/day per-IP quota shared across tools with no API key needed.

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?

It is front-loaded with what is returned and every sentence carries information — nothing is filler. The middle section is dense, using inline enum-style notation ('needs_place': no place named; ...) that takes effort to parse, which keeps it just short of a 5.

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

Completeness5/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 fully documents the return shape (per-candidate label fields, status values, reasons) and the downstream handoff to call_api. For a zero-required-parameter discovery tool, an agent has everything needed to call it and interpret every response branch.

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 the baseline is 3. The description explains the interaction between query and the measure/place/period parts and clarifies why a related_only candidate has no call_api arguments, but it does not add format or constraint detail (e.g. limit bounds, period syntax) beyond what the schema already states.

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 ('Returns up to 10 data series') plus the exact payload fields each candidate carries and the shape of the status field. It also implicitly separates itself from call_api by saying candidates carry 'the call_api arguments that return exactly that series' rather than the values themselves.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'When to use' is spelled out with the alternative path: pass query or measure/place/period, pick the candidate whose measure, place and time match, then hand its call_api arguments to call_api. It also gives the fallback behavior when status is 'none' (tell the user the service does not have it) and explains how to use a 'needs_place' none to fill in a placeholder.

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