Skip to main content
Glama

prime_check

Read-onlyIdempotent

Determine whether a non-negative integer up to 1 trillion is prime, retrieve its prime factorization, and identify adjacent primes for number theory and validation tasks.

Instructions

Check if a number is prime, get its factorization, and find adjacent primes.

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

Input Schema

NameRequiredDescriptionDefault
numberYesNon-negative integer to check (max 1 trillion).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds no further behavioral context such as the cost of factorization for large inputs, the meaning of 'adjacent primes' (nearest? next/previous?), or what output format to expect. It merely restates the operations.

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?

The description is a single, front-loaded sentence with no filler. It efficiently lists the three capabilities, though the bundling of multiple operations makes it slightly less crisp than a single-purpose description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description should explain return values, but it does not. An agent cannot tell whether all three results are always returned, whether factorization is omitted for primes, or how adjacent primes are represented. For a multi-purpose math tool with no output schema, this is a significant gap.

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 the parameter constraints (non-negative integer, max 1 trillion) are fully documented in the schema. The description adds no extra meaning about the number parameter, which is appropriate given schema completeness; baseline 3 applies.

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 set of operations on a number resource: primality check, factorization, and adjacent primes. It is clear what the tool does, but it does not differentiate from siblings like prime_factor or miller_rabin_test, leaving ambiguity about when to choose this combined tool.

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?

There is no guidance on when to use this tool versus alternatives. Sibling tools such as prime_factor and miller_rabin_test overlap with its functionality, and the description provides no conditions for selecting one over another.

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

Deploy Server

Other Tools