Scientific Calculator

Prime Checker

calculator_prime_check

Read-only

Check whether an integer is prime. Numbers < 2 are not prime.

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": {
      "n": "<n>"
    },
    "name": "calculator_prime_check"
  }
}

Input Schema

Name	Required	Description	Default
`n`	Yes	Integer to test.

Output Schema

Name	Required	Description	Default
`n`	Yes
`result`	Yes
`is_prime`	Yes
`expression`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful edge-case behavior that numbers below 2 are not prime. It does not add further behavioral context such as performance characteristics, but given the annotations and output schema, this is adequate.

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 two short sentences with no wasted wording. It front-loads the main purpose and follows immediately with the key edge condition.

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 one-parameter, read-only predicate tool with an output schema and safety annotations, the description is nearly complete. It covers the core operation and the main edge case. It does not explicitly route callers to calculator_prime_factors, which is a minor gap but not material to correct invocation.

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 description coverage is 100%, and the single parameter 'n' is already documented as 'Integer to test.' The description reinforces that the input is an integer but adds no additional syntax, range, or format guidance beyond the schema. With full schema coverage, baseline 3 is appropriate.

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 states a specific verb and resource: it checks whether an integer is prime. This clearly identifies the operation. It does not explicitly distinguish itself from the sibling calculator_prime_factors, which is the closest related tool, but the core purpose is 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?

The description supplies an important domain rule ('Numbers < 2 are not prime') but does not state when to use this tool versus calculator_prime_factors or other factorization tools. Usage is implied by the name and description, not explicitly guided.

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

All Scientific Calculator tools Inspect

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.