Affine Earth Math Court Remote

solve_shear_closure

Read-onlyIdempotent

Affine.Earth — UUM-8D Bijective Shear Closure Solver: Evaluates y = Ax + tau and x = A^-1(y - tau) in exact Int128 arithmetic with zero IEEE-754 floats (Delta == 0, BornRes == 0, Chi == +1 [CALORIE]). Auto-normalizes integer-equivalent decimals or strings at the ingress boundary.

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": {
      "y": "<y>",
      "ax": "<ax>",
      "tau": "<tau>"
    },
    "name": "solve_shear_closure"
  }
}

Input Schema

Name	Required	Description
`y`	Yes	Total observed integer state y
`ax`	Yes	Conserved linear bedrock Ax
`tau`	Yes	Inhomogeneous boundary shear tau

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior. The description adds genuine context: exact Int128 arithmetic with no IEEE-754 floats, and automatic coercion of integer-equivalent decimals or strings at ingress. It stops short of clarifying what is actually returned (the Delta/BornRes/Chi invariants are asserted but never defined), leaving the outcome semantics opaque.

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

Conciseness3/5

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

It is a single compact sentence with the core operation front-loaded, so nothing is padded. But the density comes at the cost of readability: undefined acronyms and invariant names displace information an agent actually needs.

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 carries the burden of explaining results, and it only gestures at them via undefined symbols (Delta, BornRes, Chi). For a 3-required-parameter verifier the input side is adequately covered, but an agent cannot predict the response shape or how failure is signalled.

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%, with each of y, ax and tau already documented as integer state, bedrock and shear. The description's equation y = Ax + tau restates that relationship but adds no format, range, or unit guidance beyond the schema, so the baseline 3 applies.

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?

It names a specific verb ("Evaluates") and a specific mathematical object (bijective shear closure, y = Ax + tau and its inverse), so the operation is identifiable in formal terms. However, the purpose is buried in proprietary jargon ("UUM-8D", "BornRes", "CALORIE") that an agent cannot map to a real task, and no sibling is named for contrast.

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 statement of when to choose this tool over the many affine_shield* siblings, nor any exclusion or precondition (e.g., what input domain is valid, what it means for closure to hold or fail). The agent must infer usage from the formula alone.

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?