Skip to main content
Glama

inflation_calc

Calculate how inflation changes the purchasing power of money over time. Provide an amount and dates to get the inflation-adjusted value.

Instructions

inflation calc — Finance & Math tool. Costs $0.001 USDC via x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNoTool parameters as JSON object
Behavior2/5

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

The only behavioral detail disclosed is the cost ('Costs $0.001 USDC via x402'), which is useful but not sufficient. With no annotations present, the description fails to convey the tool's side effects, required inputs, or return behavior, leaving the agent in the dark about the tool's actual operation.

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

Conciseness2/5

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

The description is extremely short, but this is under-specification rather than conciseness. The two phrases do not earn their place as they contribute minimal information, and no structure or front-loading of key details is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a financial calculator with likely multiple inputs and no output schema or annotations, yet the description offers no information about inputs, outputs, or behavior. It is completely inadequate for an agent to invoke the tool correctly, especially given the complexity of inflation calculations.

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

Parameters1/5

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

The input schema only defines a generic 'params' object with the unhelpful description 'Tool parameters as JSON object'. Neither the schema nor the description provides any details about actual parameters (e.g., amount, years, inflation rate), so the agent has no idea what arguments to supply.

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

Purpose2/5

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

The description 'inflation calc — Finance & Math tool' essentially restates the tool name and adds only a generic category label. It does not state what the tool actually does, such as calculating inflation-adjusted values, and fails to distinguish it from the many other finance/math calculators in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives like loan_calculator or convert_currency. The description provides no context, prerequisites, or exclusionary conditions, leaving the agent without any basis for tool selection.

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/gadgethumans-dev/gadgethumans-mcp'

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