Skip to main content
Glama

General Average for agent fleets

subscribe

Activate/renew a fleet: $29/mo x402 payment (X-PAYMENT header on the MCP request, signed by the account's registered wallet)

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": "subscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
fleet_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add important behavior: a $29/mo x402 payment, an X-PAYMENT header on the MCP request, and wallet-signed authorization. It still omits renewal semantics, failure behavior, idempotency, and whether the payment header is required on every invocation.

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?

The description is a single front-loaded sentence with no wasted text; the action and payment details are immediately visible. The parenthetical efficiently carries the authentication and payment context.

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

Completeness3/5

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

For a payment-gated activation tool with no annotations and no output schema, the description covers the critical payment mechanism and wallet signing requirement. It remains incomplete on sibling routing, fleet_id semantics, renewal behavior, and what the agent should expect after invocation.

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

Parameters2/5

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

There is one parameter, fleet_id, and schema description coverage is 0%, so the description must compensate. It mentions the fleet concept but does not explain what fleet_id is, its format, or how to obtain it, leaving the parameter semantics mostly implied.

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 states a specific action and resource: activating or renewing a fleet, with the payment mechanism included. It does not differentiate this from sibling tools such as enroll_fleet or fleet_status, so it falls short of the top score.

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?

Usage is implied by "Activate/renew a fleet," and the payment requirement gives some context for when this tool applies. However, there is no explicit guidance on when to use this instead of enroll_fleet, fleet_status, or other fleet-related siblings, and no exclusions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources