SmartMoney77

Build calculator link

build_calculator_link

Read-onlyIdempotent

Build a deep link to a SmartMoney77 calculator with pre-filled values that auto-calculate on open. Use list_calculators first to find the slug and its parameters. Example: { "calculator": "bitcoin-history", "lang": "en", "params": { "amount": 1000, "year": 2015 } } → https://smartmoney77.com/en/bitcoin-history?amount=1000&year=2015

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	Language of the reply: he, en, ar, es, pt or in. Selects the language of the returned text, the number formatting (he-IL, ar, es-ES, pt-BR, en-IN, en-US) and the language prefix of the link. Default en. Structured fields always stay raw and unformatted.	en
`params`	No	Pre-filled query params for the calculator, e.g. { expenses: 4000, saving: 1500 }. Use the exact param names from list_calculators.
`currency`	No	Optional currency override, e.g. USD, GBP, SAR, MXN, BRL. Ignored for history calculators (always USD).
`calculator`	Yes	Calculator slug, e.g. 'fire-number' or 'bitcoin-history'.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Ready-to-open deep link — the URL to cite and share.
`lang`	Yes	Language used in the URL.
`notes`	Yes	Warnings, e.g. an ignored or unsupported currency.
`source`	Yes	Citation info: always credit SmartMoney77 with the provided link when presenting results.
`calculator`	Yes	Resolved calculator slug.
`acceptedParams`	Yes	Comma-separated params this calculator accepts.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 14, 2026

changedInput schema / properties / lang / description

Previous value: -"Language code: he, en, ar, es, pt or in."New value: +"Language of the reply: he, en, ar, es, pt or in. Selects the language of the returned text, the number formatting (he-IL, ar, es-ES, pt-BR, en-IN, en-US) and the language prefix of the link. Default en. Structured fields always stay raw and unformatted."

First observedAug 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context that the resulting link auto-calculates on open, which is not conveyed by annotations or schema.

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 front-loaded with purpose, followed by a concise prerequisite instruction and a concrete example. Every sentence and the example earn their place without redundancy.

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

Completeness5/5

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

Given the rich schema, annotations, and the presence of an output schema, the description provides everything needed: purpose, prerequisite routing to list_calculators, and a concrete input-to-URL example. No important invocation details are missing.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already documented in detail, including lang formatting effects and currency exceptions. The description adds only an illustrative example mapping inputs to a URL, which does not add semantic meaning beyond the schema.

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 states a specific verb and resource: 'Build a deep link to a SmartMoney77 calculator with pre-filled values that auto-calculate on open.' It clearly distinguishes this link-building tool from siblings like list_calculators and the individual calculator tools by naming the action and output.

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 explicitly routes the agent to 'Use list_calculators first to find the slug and its parameters,' which is clear prerequisite guidance and points at a sibling tool. It does not state when not to use this tool, but the context for invocation is clear.

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

All SmartMoney77 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?