SmartMoney77

Build social share pack

build_share_pack

Read-onlyIdempotent

Build everything needed to share a SmartMoney77 calculation on social media in one call: the deep link to the result, a ready-to-embed 1200x628 image URL rendered on our servers, a link that opens the on-site share modal (1200x628, 1080x1080, 1080x1920 downloads), and a localized caption with attribution. Works for all 31 calculators. Example: { "calculator": "fire-number", "lang": "en", "params": { "expenses": 4000, "saving": 1500 } }

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
`emoji`	No	Optional emoji to open the caption with. Defaults to a chart emoji.
`params`	No	Calculation params to pre-fill, e.g. { amount: 1000, year: 2015 }. Same names as build_calculator_link.
`currency`	No	Optional currency override, e.g. USD, ILS, BRL. Ignored for history calculators (always USD).
`calculator`	Yes	Calculator slug, e.g. 'fire-number' or 'bitcoin-history'. Use list_calculators to discover slugs.

Output Schema

TableJSON Schema

Name	Required	Description
`lang`	Yes
`notes`	Yes
`sizes`	Yes	Every image size, each with a direct server-rendered PNG URL.
`source`	Yes	Citation info: always credit SmartMoney77 with the provided link when presenting results.
`caption`	Yes	Localized, ready-to-post social caption including the link and attribution.
`shareUrl`	Yes	Deep link to the calculated result — the URL to cite.
`calculator`	Yes
`ogImageUrl`	Yes	Server-rendered 1200x628 PNG of this result. Safe to embed directly.
`downloadUrl`	Yes	Opens the result with the share modal already open, offering all three image sizes.

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

A3.8/5.0

Behavior4/5

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

Annotations already declare it a safe, idempotent, closed-world read. The description adds real behavioral context beyond them: the image is 'rendered on our servers', the share-modal link serves three download sizes, and the caption is localized with attribution. It also notes the results are one call rather than multiple round trips.

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

Conciseness4/5

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

One dense but well-formed sentence front-loads the outcome and enumerates the returns, followed by a compact scope statement and a single inline example. It is slightly long but every clause carries distinct information; no filler.

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?

With an output schema and full annotation coverage already present, the description supplies everything else an agent needs: the four artifacts produced, calculator coverage, and a call example. Only the relationship to build_calculator_link as a lighter alternative is left implicit.

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?

Schema description coverage is 100%, so the baseline is 3, but the description adds a concrete worked example payload and cross-references build_calculator_link for param naming, which helps an agent construct the nested params object correctly.

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 states a specific verb and resource ('Build everything needed to share a SmartMoney77 calculation on social media') and enumerates the exact deliverables: deep link, 1200x628 image URL, share-modal link, and localized caption. It is clearly distinguishable from the calculator compute tools, though it never explicitly contrasts itself with the nearest sibling build_calculator_link beyond borrowing its param names.

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

Usage Guidelines3/5

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

'Works for all 31 calculators' scopes the tool but gives no when-to-use guidance, no prerequisites, and no statement of when to prefer build_calculator_link (link only) over this heavier share-pack call. Usage is implied by the phrase 'share on social media' rather than stated.

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?