list_calculators
List available calculators, optionally filtered by category
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Filter by category (e.g., 'finance', 'math') |
calculator
by com.mcpcalc
TDQS
A3.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only states the action and optional filter, without disclosing read-only nature, return format, or any side effects. Minimal behavioral context is added beyond the bare listing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence, front-loaded with the verb and resource, and contains no waste. Every word contributes meaning.
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 simple listing tool with one optional parameter and no output schema, the description is adequate. It lacks details on what 'available' means or the return structure, but given the low complexity and schema coverage, it is sufficiently complete.
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 schema already describes the 'category' parameter with examples ('finance', 'math') and indicates it is optional. The description adds the word 'optionally' which matches schema, but offers no additional semantic value beyond what the schema provides, so baseline 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 'List' and identifies the resource as 'available calculators', with an optional category filter. It clearly distinguishes this from sibling tools like calculate_cas and get_calculator_schema by focusing on enumeration rather than computation or schema retrieval.
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 implies usage through its verb and optional filter, but does not explicitly state when to use this tool versus alternatives or provide exclusions. There is no discussion of when not to use it or reference to sibling tools.
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.
TDQS
B3.3/5.0
Disambiguation2/5
The three calculation tools (calculate, calculate_cas, calculate_cas_headless) overlap significantly, with calculate_cas_headless being an explicit alias of calculate_cas. An agent may struggle to choose between them. Other session tools are distinct, but the calculation ambiguity lowers the score.
Naming Consistency4/5
Most tools follow a verb_noun pattern (list_calculators, create_session, get_session_state). Minor deviations exist, especially calculate_cas_headless with the 'headless' modifier and calculate lacking a noun, but the overall pattern is predictable.
Tool Count4/5
With 10 tools, the count is reasonable for a calculator service with session management and CAS features. However, the presence of an alias tool (calculate_cas_headless) makes the set slightly redundant, though not overstuffed.
Completeness4/5
The surface covers core calculation, CAS evaluation, prefilled URL generation, and session lifecycle (create, push, get state, close). Minor gaps exist, such as no explicit session listing, but most workflows can be completed without workarounds.