Skip to main content
Glama

register_trusted_agent

Adds or updates an authorized agent’s public key and role in a workspace trusted agent registry, enabling controlled identity and access verification.

Instructions

Registers or updates an authorized agent public key and role in the workspace trusted agent registry.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agentId": "<agentId>",
      "name": "<name>",
      "role": "<role>",
      "publicKeyPem": "<publicKeyPem>"
    },
    "name": "register_trusted_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesHuman-readable display name for the agent.
roleYesAgent functional role (e.g. "security_auditor", "tester", "architect").
agentIdYesUnique agent identifier (e.g. "agent:security-auditor-1").
metadataNoOptional metadata dictionary.
expiresAtNoOptional ISO timestamp after which the agent key expires.
publicKeyPemYesPEM-encoded public key of the agent.
workspacePathNoOptional workspace path root.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full behavioral burden, and it omits most of it. "Registers or updates" hints at upsert semantics, but nothing is said about permissions, what happens when the same agentId is re-registered with a different key or role, or whether existing trust decisions are invalidated.

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?

One front-loaded sentence, no filler and no repetition of the title. It is well structured but so terse that it leaves obvious gaps unaddressed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a security-sensitive mutation that touches the trusted agent registry, with seven parameters, a nested metadata object, and no annotations or output schema. The description says nothing about authorization requirements, the meaning of expiresAt expiry, or what a successful registration returns, so it is too thin for the tool's complexity.

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 100%, so all seven parameters, including metadata, expiresAt and workspacePath, are already documented, which sets the baseline at 3. The description only names the public key and role, adding no semantics beyond what the schema provides.

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?

The description gives a specific verb pair ("Registers or updates") and a specific resource ("authorized agent public key and role in the workspace trusted agent registry"), which is enough to distinguish it from revoke_trusted_agent in the sibling list. It stops short of naming that sibling or any boundaries explicitly.

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?

Use is heavily implied by the verb: create a registry entry, or revise an existing one. There is no statement of when to call it instead of revoke_trusted_agent, no prerequisites such as admin or workspace-owner authorization, and no guidance on renewing an expired key versus registering a new agent.

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