Skip to main content
Glama

Affine Earth Math Court Remote

verify_grover

Read-onlyIdempotent

QC-002 Grover presented-oracle verifier: oracle is a 0/1 string of length 2..8 and marked is the unique 1-index. Floats refused.

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": {
      "marked": "<marked>",
      "oracle": "<oracle>"
    },
    "name": "verify_grover"
  }
}

Input Schema

NameRequiredDescriptionDefault
markedYes
oracleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / marked / description
      Removed value: -"0-based index of that single 1, decimal, e.g. 2 for oracle 0010"
    • removedInput schema / properties / oracle / description
      Removed value: -"0/1 string of length 2..8 with exactly one 1, e.g. 0010"
  2. Changed2 schema fields changed
    • addedInput schema / properties / marked / description
      Added value: +"0-based index of that single 1, decimal, e.g. 2 for oracle 0010"
    • addedInput schema / properties / oracle / description
      Added value: +"0/1 string of length 2..8 with exactly one 1, e.g. 0010"
  3. Changed2 schema fields changed
    • removedInput schema / properties / marked / description
      Removed value: -"0-based index of that single 1, decimal, e.g. 2 for oracle 0010"
    • removedInput schema / properties / oracle / description
      Removed value: -"0/1 string of length 2..8 with exactly one 1, e.g. 0010"
  4. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  5. Changed1 schema field changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  6. Changed3 schema fields changed
    • addedInput schema / properties / marked / description
      Added value: +"0-based index of that single 1, decimal, e.g. 2 for oracle 0010"
    • addedInput schema / properties / oracle / description
      Added value: +"0/1 string of length 2..8 with exactly one 1, e.g. 0010"
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "marked",
      +  "oracle"
      +]
  7. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that floats are refused and constrains oracle length, but it does not describe the verification result or error behavior beyond that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; every clause adds a constraint or scope detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter verifier with no output schema, the description gives enough to construct valid inputs but does not state what the tool returns or how verification failure is reported. Annotations cover safety, but the missing return semantics is a real gap.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry parameter meaning; it explains oracle as a 0/1 string of length 2..8 and marked as the unique 1-index. It still leaves the exact string format of marked somewhat implicit, but it substantially compensates for the bare schema.

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 verification operation (Grover presented-oracle verifier) and identifies the two inputs, which distinguishes it from the many other verify_* siblings by algorithm. It does not fully spell out what a successful verification means, so it is not a 5.

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?

No explicit when-to-use or when-not-to-use guidance is given, and no alternative tool is named. The constraints on oracle length and marked uniqueness imply valid input but do not tell an agent when this verifier is the right choice.

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