Skip to main content
Glama
agent-passport-system

agent-passport-system-mcp

by agent-passport-system
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Create Access Receipt

create_access_receipt
Read-onlyIdempotent

Create a signed access receipt that records content reference, terms, and revocation policy after verifying the governance block and publisher key; refuse to sign if verification fails.

Instructions

Create a signed receipt recording the supplied content reference and terms, after verifying the governance block against the content and the publisher's key. If the block does not verify, the tool refuses and signs nothing. The receipt captures the block's terms and revocation policy at access time. The tool signs the receipt with agentPrivateKey but returns only a text summary (receipt ID, agent DID, publisher DID, intended usage, governance block status, training term, cached-copy revocation policy). The full signed receipt, including its signature, is not returned. A verified block is not permission to perform intendedUsage, and the receipt is not proof that access happened.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blockYesGovernance block JSON string
contentYesContent the governance block covers, used to verify its content hash
sourceUrlYesURL where content was accessed
intendedUsageYesHow you intend to use this content
agentPublicKeyYesYour agent's Ed25519 public key (hex)
agentPrivateKeyYesYour agent's Ed25519 private key (hex)
publisherPublicKeyYesPublisher's Ed25519 public key (hex), used to verify the block signature

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv8.0.0
    • addedInput schema / properties / content
      Added value: +{
+  "description": "Content the governance block covers, used to verify its content hash",
+  "type": "string"
+}
    • addedInput schema / properties / publisherPublicKey
      Added value: +{
+  "description": "Publisher's Ed25519 public key (hex), used to verify the block signature",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "agentPublicKey",
-  "agentPrivateKey",
-  "block",
-  "sourceUrl",
-  "intendedUsage"
-]New value: +[
+  "agentPublicKey",
+  "agentPrivateKey",
+  "block",
+  "content",
+  "publisherPublicKey",
+  "sourceUrl",
+  "intendedUsage"
+]
  2. Changed2 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
  3. Addedv2.8.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, idempotent), and the description adds substantial context beyond them: refusal-with-no-signature on failed verification, the signing key used, exactly which fields the returned text summary contains, and the fact that the full signed receipt/signature is withheld. It also discloses semantic limits (no permission implied, not proof of access) that no annotation conveys.

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 core action and its precondition are front-loaded, followed by return shape and then caveats, in four purposeful sentences with no filler. Length is justified by a 7-parameter signing tool with no output schema.

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 no output schema, the description compensates by enumerating the returned summary fields and clarifying that the signature is not returned, plus documenting the failure path. Nothing an agent needs to call it correctly and interpret the response appears to be missing.

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 100%, so the baseline is 3, but the description goes further by explaining the relational roles: block is verified against content and publisherPublicKey, and agentPrivateKey is what signs the receipt. It adds meaning about how parameters interact rather than just restating their types.

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+resource (create a signed access receipt) plus the precondition (governance block verification against content and publisher key). This clearly distinguishes it from sibling tools like verify_governance_block, generate_governance_block, or create_access_snapshot, which only verify or capture without issuing a signed receipt.

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 rather than stated: the description tells you verification must succeed first and that a verified block 'is not permission to perform intendedUsage,' which hints at the post-verification position in a workflow. However, it never explicitly says when to choose this tool over verify_governance_block, check_usage_permitted, or create_access_snapshot, so the routing decision is left to inference.

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