Skip to main content
Glama

webbersites-x402-data-api

by io.github.webberdesign

post_calc_finance

Exact financial + token math. POST {op:…}: compound (growth with per-period contributions), amortize (payment, total interest, schedule), npv, irr (deterministic bisection) — and token_units: exact decimal↔base-unit conversion via BigInt for any token decimals (ETH 18, USDC 6), the 18-decimal math that float64 silently corrupts. Iterative series computed exactly, never guessed. ($0.005 per call, paid via x402)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opYescompound | amortize | npv | irr | token_units
toNotoken_units — base | decimal
rateNoannual %, e.g. 6.5
yearsNo
amountNotoken_units — decimal or base-unit string
decimalsNotoken_units — ETH 18, USDC 6
cashflowsNonpv/irr — period 0 first
principalNo
periods_per_yearNodefault 12
contribution_per_periodNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
opNo
npvNo
decimalNo
irr_pctNo
scheduleNo
base_unitsNo
future_valueNo
total_interestNo
payment_per_periodNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=false, destructiveHint=false; description adds that it computes exactly via BigInt and iterative series, discloses cost per call, and names algorithms (bisection for IRR). No contradictions.

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?

The description is concise (three sentences) and front-loaded with purpose, then details operations and cost. Every sentence adds value without redundancy.

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?

Given 10 parameters and an output schema, the description covers core functionality well. It explains multiple use cases but does not detail return format (handled by output schema). Adequate for the complexity.

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?

With 70% schema coverage, the description adds meaning for the 'op' parameter by explaining each operation, and for 'token_units' it clarifies conversion. Other parameters rely on schema descriptions, which are adequate.

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 exact financial and token math, listing specific operations (compound, amortize, NPV, IRR, token_units). It distinguishes from sibling tools which are mostly GET or other POST tools with different purposes.

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?

The description explains when to use for precision (exact math avoiding float64 corruption) and mentions cost. It does not explicitly state when not to use or compare to sibling tools like get_calc, but the context is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All webbersites-x402-data-api toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes, but the SEO-related tools (head_check, full_audit, site_audit, etc.) overlap in scope, potentially causing confusion despite clear descriptions.

Naming Consistency5/5

Tool names consistently follow a get_/post_/delete_ verb pattern with descriptive noun phrases (e.g., get_seo_head_check, post_store_collection), with no mixing of naming conventions.

Tool Count2/5

With 46 tools covering a wide breadth of domains (SEO, accessibility, music, crypto, linting, etc.), the count is excessive for a single server, feeling unfocused and heavy.

Completeness4/5

The tool set covers most core operations for each sub-domain, but minor gaps exist (e.g., missing update for datastore, limited music operations).

Resources