Skip to main content
Glama

Affine Earth Math Court Remote

ast_code_verifier

Read-onlyIdempotent

Affine.Earth Pure-Swift Deterministic AST Code Verifier: synthesizes deterministic zero-float Python/Swift/SQL code and validates structural syntax, indentation, identifier scope, and algebraic doctests directly in Swift.

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": {
      "prompt": "<prompt>"
    },
    "name": "ast_code_verifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesFunction signature, docstring, and specification or code patch to synthesize or verify

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already disclose that the tool is read-only, idempotent, closed-world, and non-destructive. The description adds useful behavioral detail by specifying deterministic zero-float synthesis and structural/doctest validation directly in Swift, but it does not explain outputs, failure behavior, or any operational constraints such as limits.

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?

The description is a single dense sentence, so it is not excessively long, but it front-loads branded phrasing and repeats title-like information before the actionable content. Some of the wording, such as 'Pure-Swift Deterministic AST Code Verifier', duplicates the title rather than helping the agent decide or invoke.

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, yet the description does not say what the verifier returns: diagnostics, a pass/fail result, synthesized code, or structured errors. It also leaves the relationship between synthesis and verification unclear, which matters for a single-prompt tool that may produce or validate code.

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?

The single prompt parameter is fully described in the schema as containing a function signature, docstring, specification, or code patch. The description does not add meaningful syntax, format, or content constraints beyond what the schema already states, so the baseline 3 is appropriate.

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 specific operations (synthesize and validate) and concrete resources/languages (Python, Swift, SQL code) plus validation targets such as syntax, indentation, scope, and doctests. It is more specific than a tautology, but it does not clearly distinguish this verifier from nearby code tools such as code_ir_equiv or explain whether synthesis or verification is primary.

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 states capabilities but gives no explicit guidance on when to use this tool instead of alternatives, nor when not to use it. Sibling tools are present, but the definition does not route the agent among them.

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