Skip to main content
Glama
Sign In
Agent Compliance Passport MCP

Agent Compliance Passport MCP

by CSOAI-ORG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

issue_passport

Issue a signed Ed25519 credential for an AI agent asserting compliance with frameworks like EU AI Act, GDPR, HIPAA. The passport carries agent DID, type, and article-level claim status, valid for one year.

Instructions

Issue a signed Agent Compliance Passport. The passport is a portable Ed25519-signed credential carrying the agent's DID, type, the compliance frameworks it asserts conformance to, and per-article claim status. Valid for 365 days by default.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "issue_passport"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimsNoMap of framework -> article -> status (compliant | in_review | self_declared | remediation_in_progress | non_compliant).
agent_idNoDID-style identifier. Auto-generated if omitted.
agent_typeNollm_agent
frameworksNoFrameworks this passport asserts. Defaults to all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It describes the passport (Ed25519-signed, 365-day validity) but does not disclose side effects, idempotency, rate limits, or whether issuance stores the passport. Adequate but lacks depth.

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?

Two sentences, front-loaded with the main action, no unnecessary words. Every sentence adds value, achieving optimal conciseness.

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?

Given 4 parameters (0 required), no output schema, and nested objects, the description explains the passport's components and default validity. It is mostly complete, though could clarify post-issuance behavior (e.g., storage vs. return).

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 75% (3 of 4 properties have descriptions). The description adds context about passport structure and default validity but does not significantly enhance parameter understanding beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool issues a signed Agent Compliance Passport and explains its purpose. It distinguishes from siblings (exchange_credentials, verify_passport) by focusing on creation.

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 (issuing passports) but does not explicitly state when to use this tool versus alternatives like exchange_credentials or verify_passport. No when-not-to-use guidance is provided.

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