Skip to main content
Glama

Affine Earth Math Court Remote

@exam-diffusion Dynamic 0x0A/0x0F Affine Cartridge

exam_diffusion_court

Zero-recompile M8AffineCartridge court (@exam-diffusion, 0 0x0F laws) over checked Int128 state vectors.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "exam_diffusion_court"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_8dNo
delta_8dNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it largely fails: 'checked Int128 state vectors' hints at validation and 'Zero-recompile' hints at dynamic reconfiguration, but there is no statement of side effects, determinism, failure modes, or output shape. These two fragments are the only behavioral signal an agent gets.

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 short sentence with no filler, which is structurally fine, but the compression comes at the cost of intelligibility — the front-loaded tokens are opaque codenames rather than a scope statement.

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?

With zero annotations, no output schema, and 0% parameter description coverage, the description needed to do substantial work to make this tool callable. Instead it explains neither the inputs nor the result, leaving the agent to guess how to invoke it.

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 coverage is 0% and the description says nothing about the two parameters. It never explains what x_8d is versus delta_8d, what format or arity the integer arrays must have, or what defaults apply when both are omitted (required count is 0).

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

Purpose2/5

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

The description is a pile of internal jargon ('Zero-recompile M8AffineCartridge court', '0 0x0F laws') with no plain verb and no statement of what the tool actually produces. An agent can vaguely infer affine transformation over 8-dimensional vectors, but the purpose is not stated in actionable terms and nothing distinguishes it from siblings such as affine_math_court or m8_context_lattice.

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 when-to-use guidance, no prerequisites, and no mention of alternatives or excluded cases. The reference to '@exam-diffusion' and '0 0x0F laws' is undefined, so it cannot function as a selection criterion.

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