Skip to main content
Glama

revoke_trusted_agent

Revokes a trusted agent key in the workspace registry, invalidating future endorsements and attestations and recording an audit reason.

Instructions

Revokes a trusted agent key in the workspace registry, invalidating future endorsements or attestations.

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>",
      "reason": "<reason>"
    },
    "name": "revoke_trusted_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesAudit reason for key revocation.
agentIdYesUnique agent identifier to revoke.
workspacePathNoOptional workspace path root.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully scopes the effect to *future* endorsements and attestations, implying prior ones stand, but says nothing about reversibility, required permissions, or behavior when the agentId is unknown.

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?

A single front-loaded sentence with the verb, resource, and consequence in order, and zero filler. Nothing could be removed without losing meaning.

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?

For a three-parameter mutation with no output schema and no annotations, the definition covers what is revoked and what stops working, which is the critical mental model. Reversibility and error behavior are the notable omissions.

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 three parameters (agentId, reason, workspacePath) are already documented. The description adds only the registry scope, which loosely implies that workspacePath targets where the key lives, but no new parameter-level meaning.

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 ('Revokes') and resource ('a trusted agent key in the workspace registry'), which is unambiguous and implicitly the inverse of register_trusted_agent. It does not explicitly name the sibling, so it stops short of the 5-level differentiation.

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?

No explicit when-to-use or when-not-to-use guidance, and no alternative is named. The clause 'invalidating future endorsements or attestations' implies the operational context (agent key compromise or retirement) but leaves the agent to infer it.

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