Skip to main content
Glama
smkwray

fiscus

by smkwray
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

find_series

Search the curated economic data catalog to find series IDs and datasets. Returns curated results with metadata like units, history, and access needs, or uncurated candidates when no match found.

Instructions

Search the curated catalog. Call this before guessing any series or dataset id.

    Curated results include units, history start, access needs, supported fetch tool,
    and caveat count so the next call can select the right concept. When the catalog has
    no match, uncurated candidates from the source's own search are returned under
    uncurated_upstream. BEA inventory candidates intentionally omit reviewed history,
    units, and verified_on. For keyless discovery across the Z.1 package data dictionary,
    pass family="z1".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
familyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It details what curated results include (units, history start, etc.) and explains uncurated and BEA special cases. It implies read-only behavior but does not explicitly state safety properties.

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?

The description is concise, front-loads the purpose, and every sentence adds value. No redundancy or fluff.

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?

The description covers purpose, behavior, and family parameter well. However, it omits details on 'query' (format) and 'limit' (pagination), which are relevant for a search tool. Given the output schema exists, return values are not needed, but input semantics are incomplete.

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 coverage is 0%, so description must compensate. It adds meaningful guidance for the 'family' parameter ('pass family="z1"'), but does not describe 'query' (required) or 'limit' (default 8). This leaves semantic gaps for the agent.

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?

The description clearly states 'Search the curated catalog' with a specific verb and resource. It distinguishes itself from siblings by directing to call this before guessing any series or dataset ID, setting it apart from retrieval tools like get_series.

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?

The description provides explicit guidance: 'Call this before guessing any series or dataset id' and specifies when uncurated results appear. It also gives a specific usage example for Z.1 with family='z1'. No explicit when-not, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smkwray/fiscus'

If you have feedback or need assistance with the MCP directory API, please join our Discord server