Skip to main content
Glama

Math.Tools MCP Server

Number Properties Tool

number-properties

Divisor-related properties of a number: abundant/deficient/squarefree checks, Euler's totient, divisor count/sum, aliquot sum, or whether two numbers are coprime. 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": {
      "property": "<property>"
    },
    "name": "number-properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
aNoRequired when property is 'coprime'.
bNoRequired when property is 'coprime'.
numberNoRequired for every property except 'coprime'. Must be >= 1.
propertyYesWhich property to compute. 'coprime' needs a and b instead of number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it usefully adds an authentication prerequisite (math.tools API token with numbers:* ability) that the schema does not convey. It does not state what a call returns, what happens on invalid inputs (e.g., number < 1), or rate-limit/error behavior, which leaves meaningful gaps for an unannotated tool.

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 the property list front-loaded and the prerequisite trailing; nothing is wasted. A slightly cleaner split between what-it-does and access-requirements would make it a 5.

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?

Parameters are fully specified by the schema and there is no output schema, so the description should at least hint at result shape (scalar boolean vs integer) per property. It covers scope and auth adequately but leaves the caller guessing about return values for the eight property modes.

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%, so every parameter including the property enum and the a/b/number conditional requirements is already documented in the schema. The description's mention of coprime needing two numbers merely restates that, adding no new syntax, ranges, or constraints.

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 pairing ('Divisor-related properties of a number') and then enumerates the exact computations: abundant/deficient/squarefree, totient, divisor count/sum, aliquot sum, coprimality. This narrows it against siblings like number-facts or number-theory-check without naming them, so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to pick this over number-facts, number-theory-check, or gcf-lcm, and no exclusions. The only implied routing comes from the property enum, which is schema data rather than description guidance.

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