Skip to main content
Glama

Arc passport confirm

arc_passport_confirm

Finish a passport you started before 1 Oct 2026, after the register() transaction from the old flow: pass the draft slug and the transaction hash. New passports are bought with arc_passport_buy ($0.99).

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": {
      "slug": "<slug>",
      "tx": "<tx>"
    },
    "name": "arc_passport_confirm"
  }
}

Input Schema

NameRequiredDescriptionDefault
txYes0x hash of your register() transaction
slugYesthe 12-character id from arc_passport_draft

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the prerequisite transaction and the cut-off date, but says nothing about cost for this path, gas/payment requirements, whether the action is repeatable or irreversible, or what happens if the register() tx is invalid.

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

Conciseness4/5

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

Two tight sentences with no filler: the deadline and the legacy-flow constraint come first, the alternative second. The middle clause ('after the register() transaction from the old flow') is slightly compressed but earns its place by conveying the precondition.

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 state-changing tool with no annotations and no output schema, the definition covers who-should-call-it and with what, but not what comes back, what state changes, or how failures surface. Adequate to make the call, thin on consequences.

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%, so both parameters are already documented, including that slug is the 12-character id from arc_passport_draft and tx is a 0x register() hash. The description only restates 'draft slug and the transaction hash' without adding format, validation, or matching semantics, so baseline 3 applies.

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?

States a concrete verb-and-resource (finish a passport) and pins the scope hard: only passports started before 1 Oct 2026 via the old register() flow. It also names the alternative for new passports (arc_passport_buy), so an agent can distinguish it from the two closest siblings. It never explicitly ties 'confirm' to what is being confirmed (activation? registration?), leaving a small ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition (you must have already sent the register() transaction in the old flow) and an explicit exclusion (new passports go to arc_passport_buy at $0.99). What's missing is the sibling that produces the slug, arc_passport_draft, which is only referenced in the schema.

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