Skip to main content
Glama

Stratalize Intelligence

Get Personal Savings Benchmark

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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context — external FRED/BEA source, $0.02 per-call cost, and a cryptographic settlement receipt with a verification URL. The attestation sentence reads partly as promotional boilerplate, and the return shape (fields, units, averaging window) is never characterized.

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?

Front-loaded well: what it returns comes first, then when to use it, then provenance and cost. However, the cost is stated twice ('$0.02 atomic' and '$0.02 USDC per call') and the attestation/verification sentence consumes space without helping an agent decide or invoke.

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 read tool with no output schema, the description covers purpose, use context, source and cost adequately. What's missing is the return shape — e.g. current rate value, the comparison window for the long-run average, and whether the flag is boolean.

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 tool takes zero parameters, so there is no parameter meaning for the description to add; the 4 baseline applies. Nothing in the text conflicts with the empty schema.

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?

Names the exact metric and provenance — 'BEA personal saving rate from FRED' — and states the derived outputs (long-run average comparison, above-average flag). That is a specific resource, distinguishable by topic from the other benchmark siblings, though no sibling is named to sharpen the boundary.

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?

'Use when assessing household balance sheet health, consumption durability, and macro recession risk' gives concrete analytic contexts rather than a vague 'use for analysis'. It stops short of exclusions or naming an alternative benchmark for adjacent questions, so it's clear context without routing rules.

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