Skip to main content
Glama
Sign In

SmartTools

by io.github.9thShini
OverviewDiscussionsAdmin

Salary converter

salary_calculator

Convert pay between hourly, daily, weekly, biweekly, monthly and annual. 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": {
      "amount": "<amount>",
      "period": "<period>"
    },
    "name": "salary_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesPay amount
localeNoLanguage for the source_url link (default en)
periodYesPeriod the amount refers to
hours_per_weekNoWorking hours per week (default 40)
weeks_per_yearNoPaid weeks per year (default 52)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the conversion action and a host URL (smart-tools.xyz), but fails to mention any side effects, output format, precision, or whether the operation is read-only. For a tool that likely performs calculations and returns results, this is a significant gap.

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 description is extremely concise, using one clear sentence for the core purpose. The added phrase "Runs on smart-tools.xyz" is short but not directly useful for tool invocation, so it slightly reduces efficiency. Overall, it is well-structured and front-loaded.

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 with well-documented parameters, the description is mostly adequate, but it omits any details about the return value or output behavior. Since there is no output schema, the agent must infer what the tool returns. The platform reference does not compensate for this missing return-value context.

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?

The input schema has 100% description coverage for all parameters, including enums for period and locale, and defaults for hours_per_week and weeks_per_year. The description adds no additional parameter-level detail, but the schema already handles semantics well, so the baseline score of 3 is appropriate.

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 uses the specific verb "Convert" with the resource "pay" and enumerates the exact periods (hourly, daily, weekly, biweekly, monthly, annual), making the tool's purpose unambiguous and distinguishing it from sibling converters/calculators. It is clear this is a salary/pay conversion tool, not a generic unit converter.

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?

The description clearly implies the tool is for converting pay amounts between different time periods, but it does not provide explicit when-to-use/when-not-to-use guidance or name any alternative tools. The context is sufficient for a basic calculator, but no exclusions or comparisons are given.

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