Skip to main content
Glama

Covenant / Agentic Agreements Protocol (AAP)

Use a Covenant tool

covenant_call
Destructive

Call a reviewed keyless engine tool or an existing account operation. Account actions require the current scoped bearer grant; all original signatures, permissions and idempotency checks still apply. This router cannot install code, configure a host or acquire signing authority.

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": {
      "tool": "<tool>",
      "arguments": "<arguments>"
    },
    "name": "covenant_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYes
actionNo
argumentsYes
interfaceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

With destructiveHint=true and openWorldHint=true already declared, the description usefully adds that account actions need the current scoped bearer grant and that original signatures, permissions and idempotency checks remain in force on the underlying call. This is real added value about auth and delegation semantics. It still omits what gets destroyed on a bad call, whether errors surface as router errors or target errors, and the 'idempotency checks still apply' line sits in mild tension with idempotentHint=false.

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?

Three short sentences, front-loaded with the core claim (call a reviewed tool or account operation) followed by obligations and exclusions. No filler or repetition. It is efficient, though efficiency here partly reflects how little is said.

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?

For a destructive, open-world dispatcher with a free-form nested arguments object and no output schema, the description should explain how to address the target, what the payload must contain, and what comes back. None of that is present, so an agent would have to guess at invocation shape on a tool that can cause destructive changes.

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?

Schema description coverage is 0% across four parameters, including a nested 'arguments' object, so the description carries the full explanatory burden and does not meet it. It never states that 'tool' names the target engine tool, what 'action' selects, what shape 'arguments' must take, or what 'interface' is for. Only 'arguments' and 'interface' are optional, and even that distinction is unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it is a router that calls 'a reviewed keyless engine tool or an existing account operation', which conveys the general idea of dispatch, but never identifies what 'tool', 'action' or 'interface' actually select. It does not distinguish itself from the siblings (covenant_explain, covenant_find, covenant_onboard), so an agent cannot confidently tell when this metatool is the right entry point versus a direct call.

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?

There is negative scope ('cannot install code, configure a host or acquire signing authority') but no positive when-to-use guidance, no prerequisites for choosing between the 'engine tool' path and the 'account operation' path, and no routing advice relative to the sibling tools. The agent is told what the router will not do, not when it should reach for it.

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