Skip to main content
Glama

Affine Earth Math Court Remote

amb128_codec

Read-onlyIdempotent

Affine.Earth AMB-128 Wire Codec & Chirotope Inspector: inspects 8xUInt128 LE basis epoch, surface IDs, 97-language parity, and chiByte invariants.

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": "amb128_codec"
  }
}

Input Schema

NameRequiredDescriptionDefault
surface_idNoAMB-128 surface identifier (0=chat, 1=mcp, 2=models, 3=lang_mcp)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the tool inspects invariants and language parity, but it does not describe the result shape, failure behavior, or whether missing surface_id changes scope.

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?

The description is a single front-loaded sentence with no filler or repetition. It is compact, but the high density of unexplained domain terms makes it less immediately intelligible than it could be.

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?

There is no output schema, so the description should explain what an inspector returns or how results are structured. It names the inspected artifacts but does not say what the agent will receive, which is a meaningful omission for an inspection tool.

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%, and surface_id is already documented with concrete mappings from 0 to 3. The description only echoes 'surface IDs' and does not add semantics beyond the schema, so this meets the baseline for fully documented parameters.

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 uses a specific verb, 'inspects,' and names concrete technical resources: the AMB-128 wire codec, chirotope, basis epoch, surface IDs, language parity, and chiByte invariants. It distinguishes this tool from generic sibling operations by its AMB-128-specific scope, though the dense jargon limits immediate clarity about what the inspection actually produces.

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?

The description gives no explicit when-to-use guidance, no conditions for choosing this tool over sibling inspection or verification tools, and no note about when to omit surface_id. Usage is only implied by the tool's name and the word 'inspects.'

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