Skip to main content
Glama
Sign In

General Average for agent fleets

by com.textforagents
OverviewDiscussionsAdmin

rotate_authority

Rotate a fleet's authority secret; returns the new secret once, the old secret stops working immediately

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": {
      "fleet_id": "<fleet_id>"
    },
    "name": "rotate_authority"
  }
}

Input Schema

NameRequiredDescriptionDefault
fleet_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers the two most important traits: the new secret is returned only once, and the old secret is invalidated immediately (irreversible, disruptive to anything using the old credential). It omits permission requirements, idempotency, and failure behavior, which keeps it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the action and both critical consequences front-loaded; no filler.

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 one-parameter mutation with no annotations or output schema, the definition covers the essential facts an agent needs: what is changed, what is returned, and what breaks. Preconditions and error behavior are the remaining gap.

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 coverage is 0% and the single parameter is undocumented, but the phrase 'a fleet's authority secret' implies fleet_id identifies the target fleet. That is minimal compensation; the description adds no format, source, or validation guidance for the identifier.

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?

Names a specific verb (rotate) and resource (a fleet's authority secret), and states the outcome. No sibling tool touches fleet credentials, so an agent can select it without ambiguity.

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

Usage Guidelines2/5

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

The description explains the effect but never says when to rotate, when not to, or what the prerequisite conditions are (e.g. compromised secret, scheduled rotation). The agent must infer the trigger entirely.

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

All General Average for agent fleets toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources