Skip to main content
Glama

Math.Tools MCP Server

Number Lists Tool

number-lists

The first N prime numbers, composite numbers, or palindromic numbers. 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": {
      "kind": "<kind>"
    },
    "name": "number-lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhich list to generate.
countNoHow many numbers to return. Capped server-side per kind; defaults to a sensible per-kind default.

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?

No annotations are supplied, so the description carries the burden. It does disclose the auth requirement and that count is capped server-side with per-kind defaults, which is real behavioral context, but it says nothing about output format, ordering, or error behavior when the cap is exceeded.

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?

Two short sentences with zero padding, front-loading the core capability before the auth prerequisite. Every phrase earns its place.

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 two-parameter, single-kind list generator with no output schema, the definition covers purpose, auth, and capping behavior adequately. It falls short only on selection guidance versus sibling number tools.

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 both parameters are documented there, so the baseline is 3. The description adds little beyond the schema, merely restating that the list is the 'first N' and that count is capped.

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+resource: generating the first N primes, composites, or palindromes, with the kinds spelled out. An agent can distinguish it from number-facts or number-properties, though the description never explicitly names those siblings.

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?

Gives no when-to-use guidance and no comparison to alternatives like number-facts or number-properties. The only usage context is the auth prerequisite (math.tools token with numbers:* ability), which is helpful but not selection 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