Skip to main content
Glama
agent-passport-system

agent-passport-system-mcp

by agent-passport-system
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Verify Passport Issuer Signature

verify_issuer
Read-onlyIdempotent

Verifies whether a passport was officially issued by AEOESS by checking the issuer countersignature against the published public key; self-signed passports return false.

Instructions

Verify that a passport was officially issued by AEOESS. Checks the issuer countersignature against the published AEOESS public key. Returns false for self-signed passports.

Input Schema

NameRequiredDescriptionDefault
passportYesThe signed passport object to verify

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv4.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / passport / additionalProperties
      Removed value: -false
    • removedInput schema / properties / passport / properties / issuerSignature / additionalProperties
      Removed value: -false
    • changedInput schema / properties / passport / required
      Previous value: -[
-  "signature",
-  "signedAt"
-]New value: +[
+  "passport",
+  "signature",
+  "signedAt"
+]
  2. Addedv2.8.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real value beyond them: it names the trust anchor (published AEOESS public key) and discloses the negative-case return behavior for self-signed passports.

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?

Three short sentences, zero filler, with what the tool does front-loaded and the failure case as a trailing qualifier rather than buried preamble.

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

Completeness4/5

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

The tool has a nested input object and no output schema, so the description reasonably carries more burden. It covers the trust anchor and the false-on-self-signed case, though it doesn't state the positive return (true) or what an invalid countersignature yields, leaving a small gap.

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?

Only one parameter with 100% schema description coverage, including a nested signed-passport structure whose inner fields are typed and described in the schema. The description adds no format or structural guidance about the passport object itself, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — verifying a passport's issuer countersignature against the published AEOESS public key — which cleanly separates it from the many other verify_* siblings (verify_endorsement, verify_delegation, verify_charter). The added scope detail ('officially issued by AEOESS') makes the target of verification unambiguous.

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

Usage Guidelines3/5

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

Usage is implied by the nature of the check, and the description gives one useful selection signal (self-signed passports yield false), but it never states when to reach for this versus verify_delegation or verify_endorsement, nor any prerequisite about where the passport object comes from.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools