Skip to main content
Glama
raditotev

AgentTrust

by raditotev

link_agentauth

Link a standalone trust profile to an AgentAuth identity using a signed proof JWT and access token, transferring history and scores. After linking, authenticate exclusively with AgentAuth token.

Instructions

Link a standalone trust profile to an AgentAuth identity.

Provide your AgentAuth access_token, the public_key_hex you originally registered with, and a signed_proof JWT proving you own the standalone agent's private key. Your interaction history and scores transfer to the AgentAuth identity. The standalone profile is updated to reflect the AgentAuth source. This is a one-time, irreversible operation.

After linking, authenticate exclusively with your AgentAuth token — the public key will no longer be usable for authentication.

Canonical agent ID contract: after a successful link the canonical agent_id is always the original standalone UUID. The AgentAuth UUID is stored as agentauth_id in the profile's metadata and is also returned in the response as agentauth_id. All historical scores and interactions remain attached to the canonical standalone UUID.

The signed_proof JWT must be signed with the standalone agent's Ed25519 private key (algorithm EdDSA) and contain the following claims:

  • sub: your public_key_hex (hex-encoded 32-byte public key)

  • action: the literal string "link_agentauth"

  • iat: issued-at Unix timestamp (must be within 300 seconds of now)

Example (Python)::

import jwt, time
from cryptography.hazmat.primitives.asymmetric.ed25519 import Ed25519PrivateKey

private_key = Ed25519PrivateKey.from_private_bytes(bytes.fromhex(private_key_hex))
signed_proof = jwt.encode(
    {"sub": public_key_hex, "action": "link_agentauth", "iat": int(time.time())},
    private_key,
    algorithm="EdDSA",
)

Args: access_token: Valid AgentAuth bearer token identifying the target identity. public_key_hex: Hex-encoded Ed25519 public key used during standalone registration. signed_proof: JWT signed by the standalone agent's Ed25519 private key, proving ownership of the key. Must contain sub, action, and iat claims as described above. dry_run: When True, validate everything but do not commit any changes. Returns a preview of what would happen including current scores. Defaults to False.

Returns: On success: agent_id (canonical standalone UUID), canonical_agent_id (same as agent_id), agentauth_id (AgentAuth UUID stored in metadata), merged (bool), and a confirmation message.

On ``dry_run=True``: ``dry_run`` (``true``), ``would_link_agent_id``,
``agentauth_id``, ``current_scores``, ``interaction_count``,
``capabilities``, and ``message``.

Error codes: - invalid_input: malformed public_key_hex. - proof_sig_invalid: JWT signature or content check failed. - proof_expired: JWT iat is outside the 300-second window. - key_not_found: no standalone agent registered with that public key. - already_linked: the standalone profile is already linked to AgentAuth. - authentication_failed: AgentAuth token invalid or expired.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
access_tokenYes
public_key_hexYes
signed_proofYes
dry_runNo
Behavior5/5

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

No annotations are provided, so the description fully covers behavioral traits: one-time irreversible operation, transfer of history and scores, canonical agent ID contract, authentication change, and detailed error codes.

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?

The description is well-structured with sections for purpose, steps, contract, JWT requirements, example, arguments, returns, and errors. While comprehensive, it is lengthy but earns its place.

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?

Given the complexity (4 params, no output schema, no annotations), the description is thorough: explains parameters, return values, error codes, and behavioral implications. An AI agent can correctly invoke the tool.

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

Parameters5/5

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

The description adds substantial meaning beyond the schema, including detailed explanations for each parameter, JWT claims requirements, and a Python example. This compensates for the 0% schema description coverage.

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 'Link a standalone trust profile to an AgentAuth identity,' specifying the verb and resource. It distinguishes this tool from siblings by its unique linking operation.

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

Usage Guidelines4/5

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

The description provides clear context for use, including that it is one-time and irreversible, and explicitly explains the dry-run option. It lacks explicit alternatives or when-not-to-use statements, but the context is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/raditotev/agent-trust'

If you have feedback or need assistance with the MCP directory API, please join our Discord server