Skip to main content
Glama

Niche of One Network

Run a site tool

tool_run
Read-onlyIdempotent

Run one of the site's calculators with the same formulas as its page: gumroad-fee-calculator {salePrice, affiliatePct?, discover?}, platform-rent-calculator {units, price}, tool-cost-killer {tools: [{name?, cost, seats?, billing: Monthly|Annual|One-time, status?: keep|kill}]}. Nothing is stored.

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": {
      "tool": "<tool>",
      "inputs": "<inputs>"
    },
    "name": "tool_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYes
inputsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 meaningful context beyond that: 'Nothing is stored' confirms statelessness, and 'same formulas as its page' signals the results should match the published calculator output. It omits error behavior (e.g. what happens with an invalid input shape), which keeps it from a 5.

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, front-loaded sentence: purpose first, then a compact per-variant specification with no filler. The bracket notation is terse and readable. It is information-dense to the point of being slightly cryptic on first read, but no sentence is wasted.

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?

For a 2-parameter tool with nested object inputs, no output schema and zero schema description coverage, the description supplies the full input contract, which is the critical gap. The remaining omission is what the calculators return (e.g. a computed fee or savings figure) — with no output schema in place, a brief note on the response shape would have made it complete.

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

Parameters5/5

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

Schema description coverage is 0% and the 'inputs' parameter is an untyped object, so the description carries the entire burden — and does so completely, spelling out each calculator's field set with optionality markers ({salePrice, affiliatePct?, discover?}) and inline enum values for nested fields (billing: Monthly|Annual|One-time, status?: keep|kill). This is far more than the bare enum/schema provides and is exactly what an agent needs to construct a valid nested payload.

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 uses a specific verb ('Run') and a precise resource ('one of the site's calculators with the same formulas as its page'), then enumerates the three concrete calculator variants. An agent knows exactly what class of operation this is. It stops short of a 5 only because it never explicitly contrasts itself with any sibling tool (e.g. search_site or site_browse), though the enumerated variants make its scope unambiguous.

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?

Usage is implied rather than stated: the agent can infer it should call this when it needs a fee/cost calculation matching the site's published formulas, and the per-calculator input listings implicitly guide which variant to select. There is no explicit when-to-use/when-not-to-use statement and no named alternative for cases this tool doesn't cover.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources