Skip to main content
Glama

get_category

Read-onlyIdempotent

Retrieve a FRED category's name and parent ID using its category ID. Use 0 for the root category.

Instructions

Fetch a FRED category by its id (0 is the root of the category tree): its name and parent category id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
category_idYesThe FRED category id (0 is the root of the category tree).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe category's identifier.
nameYesHuman-readable name, e.g. `"Trade Balance"`.
parent_idYesThe parent category's id. For the root category this is [`CategoryId::ROOT`] (`0`), which FRED may also omit entirely.
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive. The description adds that id 0 is the root and that the returned data includes name and parent id, which is useful behavioral context beyond the annotations.

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?

A single sentence that front-loads the action and includes parenthetical detail without redundancy. Every word earns its place.

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?

Given the tool's simplicity, rich annotations, and an existing output schema, the description covers the essential usage context completely.

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?

The schema already provides 100% coverage, describing category_id as the FRED category id with 0 as root. The description repeats the root information but adds no new parameter semantics.

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 the verb 'fetch', the resource 'FRED category', and the input 'by its id', and specifies the output fields (name and parent category id). This distinguishes it from sibling tools that fetch children, related tags, or 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?

It clearly implies usage when you have a category id and need its metadata, but does not explicitly mention alternatives or exclusions, so it stops short of full guidance.

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/ojhermann-org/ferric-fred'

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