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') |
MCPCalc
by com.mcpcalc
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral disclosure burden. It indicates a read-only 'list' operation but does not state whether it is read-only, what fields are returned, whether pagination exists, or any other behavioral traits. The description adds minimal transparency beyond the tool name.
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 sentence, front-loaded with the primary action, and contains no filler or redundant information. It earns every word.
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 list tool with one optional parameter and no output schema, the description is adequate but incomplete. It fails to specify what the returned list contains (IDs, names, categories) or any pagination/format details, which would be necessary for an agent to use the results effectively.
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 fully describes the 'category' parameter (100% coverage), so the baseline is 3. The description's phrase 'optionally filtered by category' merely restates the schema without adding new meaning or examples beyond what the schema already provides.
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 states a specific verb ('List') and resource ('available calculators'), and clearly distinguishes from siblings like 'calculate' 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 usage is implied: to discover available calculators. However, there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The optional category filter gives some context but no direct comparison with 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
calculate_cas and calculate_cas_headless are explicitly aliases, creating two tools for the same purpose. Also, calculate and generate_prefilled_url both produce prefilled URLs, so their boundaries are not fully distinct.
Naming Consistency4/5
Most tools follow a verb_noun pattern (calculate, create_session, get_session_state, list_calculators). The main deviation is calculate_cas_headless, which still fits the pattern but is an awkward alias name.
Tool Count4/5
The 10-tool count is reasonable for a calculator service with session management. However, the alias tool is redundant and could be removed without losing functionality.
Completeness4/5
The tool set covers listing calculators, getting schemas, running calculations (standard and CAS), managing sessions, and generating URLs. Minor gaps like a dedicated way to delete sessions are addressed by close_session, so coverage is adequate.