Affine Earth Math Court Remote

affine_shield1_physics_rotor

Read-onlyIdempotent

Affine.Earth — Shield 1 · M8 Symplectic Physics & RPN Court (UC Berkeley FrontierPhysics 168/168): Solves exact Stein-reduced Pythagorean Cayley Rotors (a^2+b^2-d^2 == 0) and symplectic FrontierPhysics recurrences in 34 Flicks with zero IEEE-754 floats.

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": {
      "p": "<p>",
      "q": "<q>"
    },
    "name": "affine_shield1_physics_rotor"
  }
}

Input Schema

Name	Required	Description	Default
`p`	Yes
`q`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

C2.3/5.0

Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds that it performs exact arithmetic with zero IEEE-754 floats and runs 'in 34 Flicks,' which is useful behavioral context, but it omits return format, failure conditions, and input expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single long sentence front-loaded with branding ('Affine.Earth — Shield 1 · M8 Symplectic Physics & RPN Court') rather than actionable information. The jargon and unexplained metrics reduce clarity instead of earning their place.

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?

For a specialized prover with two required, undocumented parameters and no output schema, the description is far too thin. It provides domain flavor and a performance claim but fails to explain what the tool returns or what the parameters mean.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description never explains what the required integer parameters p and q represent. Even the formula a^2+b^2-d^2 == 0 is not connected to p or q, leaving the parameters completely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and domain: it solves exact Stein-reduced Pythagorean Cayley Rotors and symplectic FrontierPhysics recurrences. However, the heavy jargon, branding, and unexplained terms like 'RPN Court' and '34 Flicks' make the actual purpose difficult to grasp, and it does not clearly distinguish itself from the metamath/physics 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?

There is no explicit when-to-use or when-not-to-use guidance, nor any named alternative tools. The only implied usage is that it handles Pythagorean rotor or symplectic recurrence problems, which is too vague for reliable tool selection.

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

All Affine Earth Math Court Remote tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?