Skip to main content
Glama

Affine Earth Math Court Remote

project_shor_twin

Read-onlyIdempotent

QC-001b Shor twin projection: post N and halfPow to project factor and cofactor via Stein GCD, or post N, factor, and cofactor to project halfPow via CRT. 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>"
    },
    "name": "project_shor_twin"
  }
}

Input Schema

NameRequiredDescriptionDefault
NYes
factorNo
halfPowNo
cofactorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / anyOf
      Removed value: -[
      -  {
      -    "required": [
      -      "N"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "N",
      -      "halfPow"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "N",
      -      "cofactor",
      -      "factor"
      -    ]
      -  }
      -]
    • removedInput schema / properties / N / description
      Removed value: -"the modulus, decimal, e.g. 15 - carried in every shape; without it there is no question"
    • removedInput schema / properties / cofactor / description
      Removed value: -"N / factor, decimal, e.g. 5; posted together with factor"
    • removedInput schema / properties / factor / description
      Removed value: -"post factor together with cofactor (e.g. 3 and 5) and the court projects halfPow by CRT"
    • removedInput schema / properties / halfPow / description
      Removed value: -"post this half (a with a^2 == 1 mod N, a != 1, N-1), e.g. 4, and the court projects factor and cofactor"
  2. Changed5 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
      +  {
      +    "required": [
      +      "N"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "N",
      +      "halfPow"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "N",
      +      "cofactor",
      +      "factor"
      +    ]
      +  }
      +]
    • addedInput schema / properties / N / description
      Added value: +"the modulus, decimal, e.g. 15 - carried in every shape; without it there is no question"
    • addedInput schema / properties / cofactor / description
      Added value: +"N / factor, decimal, e.g. 5; posted together with factor"
    • addedInput schema / properties / factor / description
      Added value: +"post factor together with cofactor (e.g. 3 and 5) and the court projects halfPow by CRT"
    • addedInput schema / properties / halfPow / description
      Added value: +"post this half (a with a^2 == 1 mod N, a != 1, N-1), e.g. 4, and the court projects factor and cofactor"
  3. Changed5 schema fields changed
    • removedInput schema / anyOf
      Removed value: -[
      -  {
      -    "required": [
      -      "N"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "N",
      -      "halfPow"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "N",
      -      "cofactor",
      -      "factor"
      -    ]
      -  }
      -]
    • removedInput schema / properties / N / description
      Removed value: -"the modulus, decimal, e.g. 15 - carried in every shape; without it there is no question"
    • removedInput schema / properties / cofactor / description
      Removed value: -"N / factor, decimal, e.g. 5; posted together with factor"
    • removedInput schema / properties / factor / description
      Removed value: -"post factor together with cofactor (e.g. 3 and 5) and the court projects halfPow by CRT"
    • removedInput schema / properties / halfPow / description
      Removed value: -"post this half (a with a^2 == 1 mod N, a != 1, N-1), e.g. 4, and the court projects factor and cofactor"
  4. Added
  5. Removed
  6. Changed6 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
      +  {
      +    "required": [
      +      "N"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "N",
      +      "halfPow"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "N",
      +      "cofactor",
      +      "factor"
      +    ]
      +  }
      +]
    • addedInput schema / properties / N / description
      Added value: +"the modulus, decimal, e.g. 15 - carried in every shape; without it there is no question"
    • addedInput schema / properties / cofactor / description
      Added value: +"N / factor, decimal, e.g. 5; posted together with factor"
    • addedInput schema / properties / factor / description
      Added value: +"post factor together with cofactor (e.g. 3 and 5) and the court projects halfPow by CRT"
    • addedInput schema / properties / halfPow / description
      Added value: +"post this half (a with a^2 == 1 mod N, a != 1, N-1), e.g. 4, and the court projects factor and cofactor"
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "N"
      +]
  7. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value with 'Floats refused' — an input-validation behavior not present in the schema — and names the underlying algorithms (Stein GCD, CRT), which hints at exact integer arithmetic. It says nothing about output shape or failure modes beyond that.

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 dense sentences: the operation and its two modes come first, with the validation constraint last. Every clause carries information; the only cost is heavy jargon ('Stein GCD', 'CRT') that assumes domain familiarity.

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?

With no output schema, the description should indicate what comes back; it implies factor/cofactor or halfPow but never states the return form, and the input encoding is unstated. For a computation tool with zero schema coverage and no annotations covering formats, this is adequate but leaves real gaps an agent would need filled before invoking confidently.

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 0% with four bare string parameters, so the description carries the burden and does partially discharge it by explaining how N, halfPow, factor and cofactor relate across the two modes. It never states numeric format or encoding (decimal vs hex, size bounds), and 'Floats refused' only indirectly implies integer-as-string values, leaving the format ambiguity unresolved.

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 names a specific verb ('project') and resource ('Shor twin', factor/cofactor/halfPow) and describes two distinct input-to-output modes, so an agent can tell what the tool computes. It does not, however, contrast itself against any sibling (e.g. verify_shor_witness or project_affine_key), so differentiation is left implicit.

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

Usage Guidelines4/5

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

It gives concrete conditional guidance: supply N + halfPow to recover factor/cofactor, or supply N + factor + cofactor to recover halfPow. That effectively tells the agent which parameter combination selects which behavior, which is the key usage decision here. It stops short of stating when not to use it or naming an alternative tool.

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