Skip to main content
Glama

Affine Earth Math Court Remote

verify_period

Read-onlyIdempotent

Multiplicative order period verifier: certifies a^r == 1 (mod N), gcd(a,N) == 1, and a^d != 1 (mod N) for all posted proper_divisors. Floats refused.

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": {
      "N": "<N>",
      "a": "<a>",
      "proper_divisors": "<proper_divisors>",
      "r": "<r>"
    },
    "name": "verify_period"
  }
}

Input Schema

NameRequiredDescriptionDefault
NYes
aYes
rYes
proper_divisorsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / N / description
      Removed value: -"modulus, decimal, e.g. 15"
    • removedInput schema / properties / a / description
      Removed value: -"base, coprime with N, decimal, e.g. 2"
    • removedInput schema / properties / proper_divisors / description
      Removed value: -"REQUIRED on the wire: comma-separated proper divisors of r that must NOT be periods (that is the order claim), e.g. 1,2 for r=4. Absent -> REFUSED_NO_INSTANCE 'missing proper_divisors'"
    • removedInput schema / properties / r / description
      Removed value: -"the presented period: a^r == 1 (mod N), decimal, e.g. 4"
  2. Changed4 schema fields changed
    • addedInput schema / properties / N / description
      Added value: +"modulus, decimal, e.g. 15"
    • addedInput schema / properties / a / description
      Added value: +"base, coprime with N, decimal, e.g. 2"
    • addedInput schema / properties / proper_divisors / description
      Added value: +"REQUIRED on the wire: comma-separated proper divisors of r that must NOT be periods (that is the order claim), e.g. 1,2 for r=4. Absent -> REFUSED_NO_INSTANCE 'missing proper_divisors'"
    • addedInput schema / properties / r / description
      Added value: +"the presented period: a^r == 1 (mod N), decimal, e.g. 4"
  3. Changed4 schema fields changed
    • removedInput schema / properties / N / description
      Removed value: -"modulus, decimal, e.g. 15"
    • removedInput schema / properties / a / description
      Removed value: -"base, coprime with N, decimal, e.g. 2"
    • removedInput schema / properties / proper_divisors / description
      Removed value: -"REQUIRED on the wire: comma-separated proper divisors of r that must NOT be periods (that is the order claim), e.g. 1,2 for r=4. Absent -> REFUSED_NO_INSTANCE 'missing proper_divisors'"
    • removedInput schema / properties / r / description
      Removed value: -"the presented period: a^r == 1 (mod N), decimal, e.g. 4"
  4. Added
  5. Removed
  6. Changed5 schema fields changed
    • addedInput schema / properties / N / description
      Added value: +"modulus, decimal, e.g. 15"
    • addedInput schema / properties / a / description
      Added value: +"base, coprime with N, decimal, e.g. 2"
    • addedInput schema / properties / proper_divisors / description
      Added value: +"REQUIRED on the wire: comma-separated proper divisors of r that must NOT be periods (that is the order claim), e.g. 1,2 for r=4. Absent -> REFUSED_NO_INSTANCE 'missing proper_divisors'"
    • addedInput schema / properties / r / description
      Added value: +"the presented period: a^r == 1 (mod N), decimal, e.g. 4"
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "N",
      +  "a",
      +  "proper_divisors",
      +  "r"
      +]
  7. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds real context beyond them: the three predicates it actually certifies (a^r == 1, gcd(a,N) == 1, a^d != 1 for each posted divisor) and an input-rejection policy ('Floats refused'). It does not say what a failure result looks like, which keeps it short of a 5.

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?

A single dense sentence with the purpose and checks front-loaded, followed by a terse input constraint. Every clause carries information; the density is high but nothing is filler.

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 self-contained arithmetic verifier the coverage is reasonable: the checked conditions and one input rule are given. However, with no output schema and no description of the returned verdict shape, an agent cannot tell whether success is a boolean, a witness, or an exception, which is the main remaining 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 coverage is 0% and all four parameters are untyped strings, so the schema alone tells an agent nothing. The description embeds N, a, r and proper_divisors in the formulas, which lets a reader infer their roles, and 'Floats refused' hints at integer-string encoding, but the argument format (radix, size limits) and the expected divisors formatting are never stated.

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?

A specific verb (certifies) and a precise mathematical object (multiplicative order period), with the exact predicate being checked spelled out. It does not name a sibling to contrast with, but the scope is narrow enough to separate it from the other verify_* tools.

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 only implied: you call it to check that r is the multiplicative order of a mod N and that no proper divisor is a smaller order. There is no explicit statement of when to prefer it over computing the order directly, nor any prerequisite or exclusion 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