Skip to main content
Glama

get_personal_savings_benchmark

Read-only

BEA personal saving rate from FRED with long-run average comparison and above-average flag. Use when assessing household balance sheet health, consumption durability, and macro recession risk. Source: FRED / BEA. $0.02 atomic. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $0.02 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), so the description's added value is the provenance (FRED/BEA), the per-call cost of $0.02 USDC, and the cryptographic attestation with a verification URL. Those are meaningful operational facts an agent cannot get from annotations, though refresh cadence and exact return shape are unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The functional content is front-loaded and efficient, but the tail is boilerplate that repeats the price twice ('$0.02 atomic' and '$0.02 USDC per call') alongside attestation and verification-URL text. Those sentences serve a billing purpose rather than helping the agent invoke the tool correctly.

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 zero-parameter lookup with no output schema, the description covers the source, the subject metric, the comparison framing, and the cost. It stops short of specifying units, frequency, or the shape of the returned payload, which an agent relying on no output schema might still want.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema takes zero parameters, so there is no parameter meaning to explain and the baseline is 4. The description correctly implies a no-argument lookup rather than suggesting any configuration.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and provenance (BEA personal saving rate from FRED) and states the derived outputs it returns (long-run average comparison and above-average flag). This distinguishes it from the many sibling get_*_benchmark tools by metric, though it never explicitly contrasts itself with a named alternative.

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 gives clear when-to-use framing: assessing household balance sheet health, consumption durability, and macro recession risk. That is real context for an agent choosing among benchmarks, but there are no exclusions or named alternatives to route away from.

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