Skip to main content
Glama

Affine Earth Math Court Remote

finance_shield_verify

Read-onlyIdempotent

Affine.Earth FinanceShield Court: verifies caller-supplied multi-currency double-entry postings (ledger array with integer minor units and p/q rational FX cross-rates), debits == credits, Plane A twin staleness lease, and y = Ax + tau conservation in exact Int128.

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

Input Schema

NameRequiredDescriptionDefault
yNo
axNo
tauNo
stageNo
debitsNo
fx_denNo
fx_numNo
ledgerNo
creditsNo
nowFlicksNo
foreign_debitsNo
helSyndromeW14No
maxLeaseFlicksNo
nbgSyndromeW14No
shardObserversNo
foreign_creditsNo
cellFlickTimestampNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / cellFlickTimestamp
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / helSyndromeW14
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / maxLeaseFlicks
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / nbgSyndromeW14
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / nowFlicks
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / shardObservers
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / ledger
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "account": {
      +        "type": "string"
      +      },
      +      "amount": {
      +        "type": "string"
      +      },
      +      "currency": {
      +        "type": "string"
      +      },
      +      "fx_base_amount": {
      +        "type": "string"
      +      },
      +      "fx_base_currency": {
      +        "type": "string"
      +      },
      +      "fx_pair": {
      +        "type": "string"
      +      },
      +      "fx_rate": {
      +        "type": "string"
      +      },
      +      "side": {
      +        "enum": [
      +          "debit",
      +          "credit"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "account",
      +      "currency",
      +      "amount",
      +      "side"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  3. Changed9 schema fields changed
    • addedInput schema / properties / ax
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / credits
      Added value: +{
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / debits
      Added value: +{
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / foreign_credits
      Added value: +{
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / foreign_debits
      Added value: +{
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / fx_den
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / fx_num
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / tau
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / y
      Added value: +{
      +  "type": "integer"
      +}
  4. Added
  5. Removed
  6. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world, and non-destructive, so the safety profile is covered. The description adds real value by enumerating what is actually checked (balance, rational FX, staleness lease, Int128 conservation). It stops short of stating what a failure looks like or what the response contains.

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 no filler, and the domain is front-loaded. However, the density of unexplained internal terminology makes it hard to parse rather than efficient; clarity is sacrificed to compression.

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?

A 17-input verification tool with no output schema, no required-parameter markers, and no parameter documentation is severely under-described. The description does not say what constitutes a pass or failure, how the exact-arithmetic claims are reported, or how zero-required-parameter calls behave.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 17 parameters at 0% schema description coverage, the description carries the full burden but only touches a handful: ledger, debits/credits, and fx_num/fx_den implied by 'p/q rational', plus y, ax, tau via the equation. Critical inputs such as stage, nowFlicks, maxLeaseFlicks, cellFlickTimestamp, helSyndromeW14, nbgSyndromeW14, shardObservers, and the foreign_* arrays are wholly unexplained.

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 names a specific verb and resource: verifies caller-supplied multi-currency double-entry postings, including debits==credits, FX cross-rates, a staleness lease, and y = Ax + tau conservation. That distinguishes it from the quantum-circuit verify_* siblings by domain. It loses a point because the named invariants (Plane A twin, staleness lease) are opaque jargon an agent cannot decode without external knowledge.

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 call this versus affine_math_court, civic_shield_audit, or the verify_* family, and no statement of preconditions. The description never says whether all listed checks run on every call or which inputs activate which check.

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