Skip to main content
Glama

GENESIS ProofRelay MCP Verifier

Adapt agent identity evidence

proofrelay.adapt_agent_identity_evidence
Read-onlyIdempotent

Map Concordium, ERC-8004, DID, domain, wallet-controller, or IAM identity references into a hash-only PREP-3 input. ProofRelay accepts identity as evidence; it does not issue identity or certify people.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identityYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / $defs
      Removed value: -{
      -  "AgentIdentityEvidenceInput": {
      -    "description": "Hash-only external agent identity evidence accepted as PREP-3 input.",
      -    "properties": {
      -      "action_binding_hash": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "description": "Optional hash binding this identity to an action bundle.",
      -        "title": "Action Binding Hash"
      -      },
      -      "agent_id_hash": {
      -        "description": "SHA-256 hash of external agent id.",
      -        "title": "Agent Id Hash",
      -        "type": "string"
      -      },
      -      "attestation_hash": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "description": "Optional identity attestation or verifier transcript hash.",
      -        "title": "Attestation Hash"
      -      },
      -      "controller_hash": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "description": "Optional controller, owner, account, or IAM subject hash.",
      -        "title": "Controller Hash"
      -      },
      -      "domain_hash": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "description": "Optional domain-control or organization reference hash.",
      -        "title": "Domain Hash"
      -      },
      -      "expires_at": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "description": "Optional ISO-8601 expiry time.",
      -        "title": "Expires At"
      -      },
      -      "issued_at": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "description": "Optional ISO-8601 issue time.",
      -        "title": "Issued At"
      -      },
      -      "non_secret_refs": {
      -        "description": "Non-secret registry or profile references.",
      -        "items": {
      -          "type": "string"
      -        },
      -        "title": "Non Secret Refs",
      -        "type": "array"
      -      },
      -      "provider": {
      -        "description": "External identity or registry evidence source.",
      -        "enum": [
      -          "concordium_agent_registry",
      -          "erc_8004",
      -          "did",
      -          "domain_control",
      -          "wallet_controller",
      -          "enterprise_iam",
      -          "other"
      -        ],
      -        "title": "Provider",
      -        "type": "string"
      -      },
      -      "registry_record_hash": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "description": "Optional registry record or metadata hash.",
      -        "title": "Registry Record Hash"
      -      },
      -      "verification_method_hash": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "description": "Optional verification method or key-reference hash.",
      -        "title": "Verification Method Hash"
      -      }
      -    },
      -    "required": [
      -      "provider",
      -      "agent_id_hash"
      -    ],
      -    "title": "AgentIdentityEvidenceInput",
      -    "type": "object"
      -  }
      -}
    • removedInput schema / properties / identity / $ref
      Removed value: -"#/$defs/AgentIdentityEvidenceInput"
    • addedInput schema / properties / identity / properties
      Added value: +{
      +  "action_binding_hash": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ]
      +  },
      +  "agent_id_hash": {
      +    "type": "string"
      +  },
      +  "attestation_hash": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ]
      +  },
      +  "controller_hash": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ]
      +  },
      +  "domain_hash": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ]
      +  },
      +  "expires_at": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ]
      +  },
      +  "issued_at": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ]
      +  },
      +  "non_secret_refs": {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  "provider": {
      +    "enum": [
      +      "concordium_agent_registry",
      +      "erc_8004",
      +      "did",
      +      "domain_control",
      +      "wallet_controller",
      +      "enterprise_iam",
      +      "other"
      +    ],
      +    "type": "string"
      +  },
      +  "registry_record_hash": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ]
      +  },
      +  "verification_method_hash": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ]
      +  }
      +}
    • addedInput schema / properties / identity / required
      Added value: +[
      +  "provider",
      +  "agent_id_hash"
      +]
    • addedInput schema / properties / identity / type
      Added value: +"object"
    • removedInput schema / title
      Removed value: -"adapt_agent_identity_evidenceArguments"
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, destructiveHint=false. The text adds useful context: it accepts evidence without issuing identity or certifying people, which is not encoded in annotations. It does not expose hashing internals, failure modes, or normalization behavior, so not a 5.

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 sentences provide the core semantics with modest structure. Some jargon ('PREP-3', 'hash-only') adds density; no fluff.

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?

Rich context: nested input schema with enums (provider variants), annotation hints, output schema true, and many sibling tools for comparison. However, no return-value explanation, error/gql edge cases, and does not clearly describe the trust-proof procedure or output hash format; the output schema exists but the narrative doesn't fully synthesize the overall result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and parameter descriptions are absent. The specification only enumerates the location of identity parameter objects; provider enum values provide top-level content, but nested fields (e.g. issuer, timestamps, hashes, register hash) have no semantic description; the documentation's 'identity' does not explain those particular fields. A fairly deep parameter gap.

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 specific verb+resource: "Map ... identity references into a hash-only PREP-3 input." It also indicates a behavioral boundary ('accepts identity as evidence; does not issue identity or certify people'). Some domain jargon ('PREP-3', 'hash-only') is not defined, and it doesn't explicitly distinguish itself from sibling tools, but the core action is clear.

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?

Notes that the tool accepts evidence and does not issue identity, which implies a read/transform role; however, it does not state when to prefer this over sibling tools, provide alternative conditions, or explicitly specify prerequisites for input identity formats.

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