Skip to main content
Glama
Sign In

OwnerSpec

by com.ownerspec
OverviewDiscussionsAdmin

Open an OwnerSpec calculator

run_calculator
Read-onlyIdempotent

Open one OwnerSpec calculator, prefilled with the user's numbers. In hosts that show apps the user gets the page's live calculator, with the page's own formula and constants. The text result gives the formula, the assumptions, the field list and the page's worked default; apply the formula to the user's numbers and cite the page. Get ids and field names from list_calculators.

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": {
      "calculator": "<calculator>"
    },
    "name": "run_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsNoField name to value, using the field names list_calculators returns (e.g. {"vol": 40, "line": 70})
calculatorYesCalculator id from list_calculators, e.g. exp-tank, or the page URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this read-only, idempotent and non-destructive, so the description isn't needed for safety. It adds real behavior the annotations can't: the host-dependent outcome (live app vs. text result), the exact contents of the text result, and the citation obligation. It doesn't say what happens when a calculator id is invalid.

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?

Front-loaded with the action and its prefill behavior, then the host-dependent result, then the follow-up instruction. Four tight sentences with no filler; the host-behavior clause is dense but carries necessary information.

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 no output schema, the description usefully describes the return payload (formula, assumptions, field list, worked default), and annotations cover the safety profile. Remaining gaps are edge cases — invalid calculator ids, error behavior, and whether the opened page persists state.

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 coverage is 100%, so both parameters are already documented, and the schema description is actually more explicit about the inputs shape than the tool description. The description adds only the provenance hint that ids and field names come from list_calculators, which the schema already states — baseline 3 applies.

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?

States a specific verb and resource ('Open one OwnerSpec calculator') and immediately scopes it ('prefilled with the user's numbers'). It also names the sibling that supplies ids and field names, so an agent can separate this from list_calculators without reading either schema.

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?

Gives clear context for use — the user's numbers are applied to the page's formula and the page is cited — and routes to list_calculators for prerequisite ids and field names. It stops short of explicit exclusions, e.g. when size_water_softener or diagnose_water_problem would be the better choice.

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

All OwnerSpec 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