Skip to main content
Glama

Covenant / Agentic Agreements Protocol (AAP)

Show a tool and how to use it

covenant_explain
Read-onlyIdempotent

Get the one recommended call for a tool: its exact arguments, a working example and what access it needs. Pass detail "full" to see every version of the tool with its exact schema. Select interface when several versions share a name.

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

Input Schema

NameRequiredDescriptionDefault
toolYes
actionNo
detailNoshort (the default) gives the recommended call; full gives every version.
interfaceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "short (the default) gives the recommended call; full gives every version.",
      +  "enum": [
      +    "short",
      +    "full"
      +  ]
      +}
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful behaviour beyond that — that only one recommended call is returned by default and that the full detail level exposes every version — but says nothing about size of output, cost, or auth/scope resolution despite mentioning access needs as a return field.

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?

Two front-loaded sentences with the return payload first and the parameter switches second; little waste. The phrase "with its exact schema" in the second sentence slightly repeats the exact-arguments idea from sentence one.

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?

No output schema exists, so the description must carry the return contract, and it does so only loosely — three named fields, no shape or pagination. Combined with an undocumented action parameter and no interface/version semantics beyond "select interface", a lookup tool with four parameters is described adequately but not fully.

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?

With 25% schema coverage, two of the four parameters carry meaning only in the description: detail is explained (short default vs full) and interface is given a selection rule. The required tool parameter is left as self-evident, and action is never mentioned anywhere, leaving a real gap the description should have closed.

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 and resource — get the recommended call for a tool — and enumerates what comes back (exact arguments, a working example, access needs). It is clear what the tool produces, though it never contrasts itself with covenant_call or covenant_find, so the agent must infer that this is a pre-flight lookup rather than an execution.

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?

Guidance is given only at the parameter level: use detail "full" for every version, and pick interface when names collide. There is no explicit statement of when to reach for this tool instead of covenant_call or covenant_find, which is exactly the ambiguity a discovery tool needs to resolve.

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