Skip to main content
Glama

Math.Tools MCP Server

Number Theory Check Tool

number-theory-check

Run a primality/shape check on a number, or get its prime factorization. Requires a math.tools API token (numbers:* ability).

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": {
      "check": "<check>",
      "number": "<number>"
    },
    "name": "number-theory-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkYesWhich check to run.
numberYesThe number to check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations present, the description does useful work by disclosing the auth requirement and ability scope, which an agent cannot get from the schema. However, it does not say the operation is read-only, whether results are cached or rate limited, or that output shape differs by check type (boolean vs. factor list).

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?

Two compact sentences with no filler, capability stated first and the prerequisite second. Nothing is padded, though the sentence is dense enough that the auth note competes with the functional description for the reader's attention.

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 2-parameter query tool with no annotations and no output schema, the description is adequate but leaves the return type unexplained – an agent cannot tell whether is-prime yields a boolean and prime-factors a list, which matters for chaining calls. Given no output schema exists, the description should carry that burden and does not.

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% and the check enum is fully self-documenting, so the schema carries the parameter semantics. The description adds only a loose grouping of the enum into 'primality/shape checks' versus 'prime factorization', which is marginal added meaning.

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?

States a specific verb and resource ('run a primality/shape check', 'get its prime factorization') and names the two operating modes of the tool. It does not name a sibling such as number-properties or number-facts, so the differentiation is only implicit, but the purpose itself 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 a real precondition ('Requires a math.tools API token (numbers:* ability)') and hints at two usage modes, but never says when to pick this over number-properties, number-facts, or number-lists. An agent must infer the boundary from tool names alone.

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