Skip to main content
Glama

Affine Earth Math Court Remote

m8_context_lattice

Read-onlyIdempotent

Affine.Earth M8ContextLattice Court: evaluates non-commutative M8 conversation fold, script/language detection across all 97 languages (9 RTL), and session recall witness.

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": {
      "text": "<text>"
    },
    "name": "m8_context_lattice"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesUtterance or query text
session_idNoSession identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

C2.7/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 a closed-world scope, so the safety profile is covered. The description adds useful context beyond that: the breadth of language coverage (97 languages, 9 RTL) and a session-recall element tied to prior context. It does not disclose what the evaluation returns, whether detection is deterministic, or what a "witness" failure means, which limits the added value.

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 identifier front-loaded, so there is no padding. However, the density of undefined terminology ("M8ContextLattice Court," "non-commutative fold") spends the sentence's budget on branding rather than information, which undercuts its structural efficiency.

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 a simple two-parameter schema, no output schema, and a read-only annotation set, the description's main remaining job is to say what the agent gets back — and it does not. An agent knows it will "evaluate" something about language and session, but not the shape, determinism, or interpretation of the result, which is a meaningful gap for a tool with no output schema to fall back on.

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 both `text` and `session_id` documented in the schema, so the baseline of 3 applies. The description only obliquely reinforces `session_id` through the phrase "session recall witness" and says nothing about how `text` is tokenized or how session scoping changes results. It adds atmosphere rather than parameter semantics.

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 verb ("evaluates") and three sub-functions: an M8 conversation fold, script/language detection over 97 languages, and a "session recall witness." The language-detection part is concrete, but "non-commutative M8 conversation fold" and "witness" are unexplained jargon, so an agent cannot form a clear picture of what the tool actually produces. It also does not distinguish itself from nearby siblings such as lattice_op or affine_translate_text, which plausibly overlap with the language-detection role.

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 guidance on when to use this tool versus the alternatives, no prerequisites, and no statement of conditions where it would be the wrong choice. "Court" and "lattice" framing implies an evaluative/verification role, but nothing tells the agent which inputs or tasks should route here rather than to lattice_op or affine_translate_text.

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