fred_categoryBrowse economic data by category (housing, employment, money/banking, etc.). Returns subcategories and related series IDs.
| Name | Required | Description | Default |
|---|---|---|---|
| _apiKey | Yes | FRED API key | |
| category_id | No | Category ID to browse children of (default: 0 for root) |
| Name | Required | Description | Default |
|---|---|---|---|
| categories | Yes | Child categories | |
| parent_category_id | Yes | Parent category ID |
Changes observed during successful MCP inspections.
Input schema / examplesPrevious value: -[
- {
- "_apiKey": "your-fred-api-key",
- "category_id": 0
- },
- {
- "_apiKey": "your-fred-api-key",
- "category_id": 113
- }
-]New value: +[
+ {
+ "category_id": 0
+ },
+ {
+ "category_id": 113
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "categories": {
+ "description": "Child categories",
+ "items": {
+ "properties": {
+ "id": {
+ "description": "Category ID",
+ "type": "number"
+ },
+ "name": {
+ "description": "Category name",
+ "type": "string"
+ },
+ "parent_id": {
+ "description": "Parent category ID",
+ "type": "number"
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "parent_id"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "parent_category_id": {
+ "description": "Parent category ID",
+ "type": "number"
+ }
+ },
+ "required": [
+ "parent_category_id",
+ "categories"
+ ],
+ "type": "object"
+}Input schema / examplesAdded value: +[
+ {
+ "_apiKey": "your-fred-api-key",
+ "category_id": 0
+ },
+ {
+ "_apiKey": "your-fred-api-key",
+ "category_id": 113
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds that it returns subcategories and series IDs, which is useful behavioral context. However, it does not disclose error behavior, traversal limits, or handling of invalid category IDs, which would enhance transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, compact sentence that front-loads the main action ('Browse economic data by category') and states the output. Every word earns its place with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple browse tool with a documented schema and an output schema (though not shown), the description is largely sufficient. It explains the purpose and the return value. Minor gaps like how to start from the root or how to interpret nested categories are not critical, as the schema already specifies the default category_id=0.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for both parameters (_apiKey and category_id), including the default of 0 for category_id. The description does not add additional meaning beyond the schema; it merely implies category_id by mentioning 'by category'. Baseline 3 is appropriate since the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb ('browse') and resource ('economic data by category'), and specifies the return value ('subcategories and related series IDs'). It is distinct from other fred tools in that it focuses on category traversal, though it does not explicitly name a sibling to differentiate itself.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives like fred_search, fred_get_series, or fred_series_info. The description does not mention scenarios where category browsing is preferred, nor does it exclude other tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.