Skip to main content
Glama
raditotev

AgentTrust

by raditotev

generate_agent_token

Generate a signed JWT access token to authenticate standalone agent calls. Provide agent ID and private key to obtain a token valid for a specified duration.

Instructions

Generate a signed access token for a standalone agent.

Standalone agents authenticate by signing short-lived JWTs with their Ed25519 private key. Call this tool to obtain an access_token that can be passed directly to report_interaction, file_dispute, issue_attestation, get_score_breakdown, and any other tool requiring authentication.

The token is signed using your private key — no key material is stored server-side. When your token expires, call this tool again.

Typical agent flow:

  1. Call register_agent() once → receive agent_id + private_key_hex

  2. Call generate_agent_token(agent_id, private_key_hex) → receive access_token

  3. Pass access_token to authenticated tools

  4. Repeat step 2 when the token expires (check expires_at)

Args: agent_id: Your agent UUID (from register_agent). private_key_hex: Your 32-byte Ed25519 private key as 64 hex chars (private_key_hex from your register_agent response). ttl_minutes: Token lifetime in minutes. Default 60, max 1440 (24 h).

Returns: access_token: Signed JWT — pass this as access_token to other tools. expires_at: ISO 8601 UTC timestamp when the token expires. ttl_minutes: Actual TTL applied after clamping.

Example call: generate_agent_token( agent_id="550e8400-...", private_key_hex="d4e5f6...", ttl_minutes=60 )

Example response: { "access_token": "eyJ...", "expires_at": "2026-03-20T13:00:00+00:00", "ttl_minutes": 60, "agent_id": "550e8400-..." }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYes
private_key_hexYes
ttl_minutesNo
Behavior4/5

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

With no annotations, the description carries the full transparency burden. It discloses that the token is signed client-side, no server-side key storage, token expiration, and the TTL clamping behavior. It does not mention rate limits or error conditions, but the provided information is sufficient for a straightforward token generation tool.

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, bullet points, and examples. While slightly verbose, every sentence contributes meaning. The clear formatting aids readability and usability.

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 tool's moderate complexity (3 parameters, no output schema), the description is remarkably complete. It covers the typical workflow, parameter details, expected response structure (including an example), and the authentication flow. No gaps are apparent.

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?

Schema description coverage is 0%, so the description must compensate fully. It does so by explaining each parameter's purpose, source (e.g., from register_agent response), format (64 hex chars for private_key_hex), and constraints (default/max for ttl_minutes). This adds substantial value beyond the bare JSON schema.

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 generates a signed access token for standalone agents. It differentiates by explaining the use case (authentication) and listing which sibling tools require the token, making it distinct from similar tools like register_agent.

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 explicit usage context: after register_agent and before calling authenticated tools. It includes a typical agent flow and advises to repeat when token expires. However, it does not explicitly state when not to use this tool or compare with alternatives, though the specific authentication role is implied.

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