Skip to main content
Glama
agent-passport-system

agent-passport-system-mcp

by agent-passport-system
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Verify Trust Anchor Bundle

mutualAuthVerifyTrustBundle
Read-onlyIdempotent

Verify a TrustAnchorBundle's signature and freshness using trusted publisher public keys, returning success or a specific failure reason.

Instructions

Verify a TrustAnchorBundle signature and freshness. Caller supplies the list of trusted publisher public keys (root configuration). Returns ok:true on success or failure reason (untrusted_publisher, signature_invalid, bundle_expired, not_yet_valid).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bundleYesTrustAnchorBundle to verify
now_msNoCurrent unix ms — defaults to Date.now()
trusted_publisher_pubkeys_hexYesList of Ed25519 pubkeys (hex) authorized to publish bundles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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
    • changedInput schema / required
      Previous value: -[
-  "trusted_publisher_pubkeys_hex"
-]New value: +[
+  "bundle",
+  "trusted_publisher_pubkeys_hex"
+]
  2. Addedv2.8.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish that the tool is read-only, idempotent, non-destructive, and not open-world. The description adds useful behavior beyond that: it explains that the tool checks both signature and freshness, states the success return value, and enumerates failure reasons. It could say more about freshness semantics, but the added failure-mode detail is valuable.

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?

The description is two tightly written sentences. It front-loads the core action, then covers caller responsibility and return behavior without any filler.

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

Completeness5/5

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

With annotations covering the safety profile and schema covering all three parameters, the description supplies the remaining needed context: purpose, required trusted-key input, success condition, and failure reason codes. No output schema exists, so explicitly describing the return values is important and is handled well.

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 description coverage is 100%, so the baseline is 3. The description adds meaning by clarifying that the trusted_publisher_pubkeys_hex list is effectively the root configuration supplied by the caller, and by identifying that the target bundle is verified for signature and freshness. The optional now_ms parameter is not discussed in the description, keeping it from a 5.

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?

The description states a specific verb+resource: verify a TrustAnchorBundle signature and freshness. It distinguishes the operation from the neighboring mutualAuth tools (BuildCertificate, VerifyAttest, DeriveSession) by naming the exact artifact and verification scope.

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?

The description implies usage by saying the caller must supply the trusted publisher public keys as root configuration, but it does not explicitly say when to choose this tool over sibling verification tools or when not to use it. It provides minimum viable context without routing guidance.

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