Skip to main content
Glama

Affine Earth Math Court Remote

by earth.affine
OverviewDiscussionsAdmin

execute_transition

Certified membrane: Rational S4/C4 lanes -> SCF boundary -> annihilate raw context -> NATS geometry-only turn -> Aristotelian projection. IDEMPOTENT: this membrane is stateless and keeps no record of a signature, so replaying an identical request is admitted and returns the identical receipt_hash rather than being refused as a replay. Safe to retry on a timeout; it is not a second transition.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intentYesthe transition verb, one of the enum values, e.g. INGEST
economicsNoOptional I_PF economics object: executor hash + impact matrix (Rational weights), keys executor_btc_address_hash and context_class, e.g. {"executor_btc_address_hash":"0123456789abcdef0123456789abcdef","context_class":"default"}
entity_idYeswallet_geo entityID hex. e.g. 0123456789abcdef0123456789abcdef
bond_statusNothe bond state the caller reports for itself, recorded with the turn; e.g. BONDED. Omitted -> UNKNOWN
c4_constraintsNoRational lanes as num/den strings. e.g. ["1/1","0/1","2/3","1/4"]
s4_coordinatesNoRational lanes as num/den strings. e.g. ["1/2","3/4","0/1","5/1"]
user_vqbit_hashNoExactly 32 lowercase hex, or OMIT it and the cell derives sha256(entity_id|scf_hex)[0:16]. A stated value that is not 32 hex is REFUSED rather than replaced - the cell will not verify your signature against an identity you did not state. e.g. 0123456789abcdef0123456789abcdef
client_signatureYessha256(INTENT|scf_hex|user_vqbit_hash|genesis_epoch) first 16 bytes as 32 lowercase hex; or the game seal sha256(INTENT|scf_hex|user_vqbit_hash); or an ML-DSA-87 IDENTITY_BIND package. scf_hex is NOT an input and is NOT a sha256: the cell derives it with SpatialChordalFingerprint (15 integer lattice ratios folded FNV-1a-128) over the NORMALISED lanes. Mirror that algorithm to sign on the first call - /language-game/scf.js is the reference port - or send any 32-hex signature once and re-sign over the scf_hex the refusal returns. genesis_epoch is 2026-01-27T00:00:00Z. e.g. 0123456789abcdef0123456789abcdef

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / bond_status / description
      Added value: +"the bond state the caller reports for itself, recorded with the turn; e.g. BONDED. Omitted -> UNKNOWN"
    • changedInput schema / properties / c4_constraints / description
      Previous value: -"Rational lanes as num/den strings"New value: +"Rational lanes as num/den strings. e.g. [\"1/1\",\"0/1\",\"2/3\",\"1/4\"]"
    • changedInput schema / properties / client_signature / description
      Previous value: -"sha256(INTENT|scf_hex|user_vqbit_hash|genesis_epoch) first 16 bytes as 32 lowercase hex; or the game seal sha256(INTENT|scf_hex|user_vqbit_hash); or an ML-DSA-87 IDENTITY_BIND package. scf_hex is NOT an input and is NOT a sha256: the cell derives it with SpatialChordalFingerprint (15 integer lattice ratios folded FNV-1a-128) over the NORMALISED lanes. Mirror that algorithm to sign on the first call - /language-game/scf.js is the reference port - or send any 32-hex signature once and re-sign over the scf_hex the refusal returns. genesis_epoch is 2026-01-27T00:00:00Z."New value: +"sha256(INTENT|scf_hex|user_vqbit_hash|genesis_epoch) first 16 bytes as 32 lowercase hex; or the game seal sha256(INTENT|scf_hex|user_vqbit_hash); or an ML-DSA-87 IDENTITY_BIND package. scf_hex is NOT an input and is NOT a sha256: the cell derives it with SpatialChordalFingerprint (15 integer lattice ratios folded FNV-1a-128) over the NORMALISED lanes. Mirror that algorithm to sign on the first call - /language-game/scf.js is the reference port - or send any 32-hex signature once and re-sign over the scf_hex the refusal returns. genesis_epoch is 2026-01-27T00:00:00Z. e.g. 0123456789abcdef0123456789abcdef"
    • changedInput schema / properties / economics / description
      Previous value: -"Optional I_PF economics: executor hash + impact matrix (Rational weights)."New value: +"Optional I_PF economics object: executor hash + impact matrix (Rational weights), keys executor_btc_address_hash and context_class, e.g. {\"executor_btc_address_hash\":\"0123456789abcdef0123456789abcdef\",\"context_class\":\"default\"}"
    • changedInput schema / properties / entity_id / description
      Previous value: -"wallet_geo entityID hex"New value: +"wallet_geo entityID hex. e.g. 0123456789abcdef0123456789abcdef"
    • addedInput schema / properties / intent / description
      Added value: +"the transition verb, one of the enum values, e.g. INGEST"
    • removedInput schema / properties / intent / enum
      Removed value: -[
-  "OPEN_CURVE",
-  "INGEST",
-  "ARISTOTELIAN",
-  "JORDAN_CLOSED",
-  "KLEIN_FLIP",
-  "FLUSH",
-  "PROTOCOL_DRILL",
-  "IDENTITY_BIND",
-  "WALLET_LOCATION_BIND",
-  "OPERATOR_TENSOR_HEAL",
-  "REALITY_PRESENCE_INTRO",
-  "REALITY_OPERATOR_HEAL",
-  "REALITY_DISAGREE_SHATTER",
-  "CINEMA_SEED_EXPORT"
-]
    • changedInput schema / properties / s4_coordinates / description
      Previous value: -"Rational lanes as num/den strings"New value: +"Rational lanes as num/den strings. e.g. [\"1/2\",\"3/4\",\"0/1\",\"5/1\"]"
    • changedInput schema / properties / user_vqbit_hash / description
      Previous value: -"Exactly 32 lowercase hex, or OMIT it and the cell derives sha256(entity_id|scf_hex)[0:16]. A stated value that is not 32 hex is REFUSED rather than replaced - the cell will not verify your signature against an identity you did not state."New value: +"Exactly 32 lowercase hex, or OMIT it and the cell derives sha256(entity_id|scf_hex)[0:16]. A stated value that is not 32 hex is REFUSED rather than replaced - the cell will not verify your signature against an identity you did not state. e.g. 0123456789abcdef0123456789abcdef"
  2. First observed

TDQS

C2.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a genuinely useful trait: statelessness, replay-admission, and a stable receipt_hash return on identical requests. However it omits side effects (what 'annihilate raw context' actually destroys), auth/identity requirements, and error behavior for a mutation-flavored tool. Useful but incomplete.

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?

Two sentences with no obvious filler, and the idempotency guarantee is stated prominently. But the opening sentence is an unbroken jargon pipeline that is hard to parse and front-loads metaphor over function, weakening structure for an agent reader.

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?

This is a high-complexity tool (8 params, nested economics object, no output schema, no annotations), yet the description never explains the domain (entity_id/intent semantics), the outcome of a transition, or the receipt beyond a passing mention. The idempotency note is valuable but leaves major gaps for such a complex signature.

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 the schema itself is extremely detailed (signature derivation, scf_hex, lattice lanes, refusal behavior), so the description adds essentially nothing about parameters. Baseline 3 applies when the schema does the heavy lifting.

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 first sentence is a chain of cryptic metaphors ('Rational S4/C4 lanes -> SCF boundary -> annihilate raw context -> NATS geometry-only turn -> Aristotelian projection') that never states in plain terms what a 'transition' accomplishes or what resource it acts on. An agent cannot tell from this what the tool is for versus the many verify_*/execute_* siblings. It is not a pure tautology, but it stops short of a usable verb+resource statement.

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 only usage guidance is retry semantics ('Safe to retry on a timeout; it is not a second transition'), which speaks to repeated invocation rather than when to select this tool over alternatives. No prerequisites, no when-not-to-use, and no sibling routing (e.g., vs membrane_health or corpus_bonds) are offered.

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 toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources