Skip to main content
Glama
Sign In

SmartTools

by io.github.9thShini
OverviewDiscussionsAdmin

Tip calculator

tip_calculator

Tip amount, total and per-person split for a bill. Runs on smart-tools.xyz.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bill": "<bill>",
      "tip_rate": "<tip_rate>"
    },
    "name": "tip_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
billYesBill amount
localeNoLanguage for the source_url link (default en)
peopleNoNumber of people to split between (default 1)
tip_rateYesTip, percent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It lists the computed values but does not disclose return format, rounding behavior, whether it operates locally or remotely, or the role of the smart-tools.xyz source URL mentioned in the locale parameter.

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?

The first sentence is concise and informative. The second sentence 'Runs on smart-tools.xyz' adds little value and could be omitted, but the overall description is short.

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

Completeness3/5

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

For a simple calculator, the output is implied but not specified in terms of structure or currency formatting. The 'source_url' hint in the locale parameter is not explained, leaving a gap in understanding the full response.

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 the schema already documents each parameter. The tool description adds no additional parameter semantics beyond confirming that people affects per-person split and tip_rate affects the tip.

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 specifies the three key outputs (tip amount, total, per-person split) for a bill, clearly distinguishing it from sibling calculators like discount or percentage. Though no verb like 'calculates' is used, the phrasing is unambiguous.

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?

No guidance is provided for when to use this tool vs alternatives like discount_calculator or margin_calculator. The description only states what it does, not the context in which it should be selected.

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

All SmartTools toolsInspect
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