Skip to main content
Glama

Math.Tools MCP Server

Number Facts Tool

number-facts

Get a trivia fact about a specific number, a batch of random integers, or today's curated number of the day. 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": {
      "action": "<action>"
    },
    "name": "number-facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoFor action 'random': maximum value, inclusive.
minNoFor action 'random': minimum value, inclusive.
totalNoFor action 'random': how many numbers to return (capped server-side).
actionYesWhich lookup to perform. 'fact' needs number; 'random' returns one or more random integers; 'number-of-the-day' returns today's curated pick.
numberNoRequired when action is 'fact' — the number to look up.
categoryNoFor action 'number-of-the-day': the category shortname. Defaults to the site's default category.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose a real operational constraint: an API token with numbers:* ability is required. That is genuinely useful context not present in structured fields. It still omits error behavior, rate limits, and what the returned facts look like (string vs. object), so it is only partially transparent.

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 sentences, zero filler, with the capability statement front-loaded and the prerequisite isolated in its own sentence. Nothing repeats what the schema already says.

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 six-parameter, multi-mode tool with no annotations and no output schema, the description correctly frames all modes and the auth prerequisite. It stops short of describing the return shape (single fact vs. list of facts for 'random'), which an agent would want before formatting results.

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 min, max, total, action, number, and category are already fully documented in the schema, and the baseline of 3 applies. The description adds no syntax, defaults, or constraints beyond echoing the mode names — for example, it never mentions the category shortname or the server-side cap on total.

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?

"Get a trivia fact" gives a specific verb and resource, and the description enumerates all three supported modes (single number, random batch, number of the day). It does not explicitly contrast itself with number-properties or number-lists, so an agent must infer the boundary from the mode list rather than being told.

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?

Usage is implied by the three named modes and reinforced by the 'action' enum documentation in the schema, which tells the agent which field each mode needs. However, there is no statement of when to prefer this over the sibling lookup tools (e.g., number-properties for mathematical properties vs. trivia).

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