Skip to main content
Glama

Covenant / Agentic Agreements Protocol (AAP)

Start with Covenant

covenant_onboard
Read-onlyIdempotent

See the available engine, marketplace and account routes. No account or key is needed to start.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "covenant_onboard"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

The annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description contributes one useful extra fact – no authentication is required – but says nothing about what the call returns, how large the result is, or what "routes" represent.

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 short sentences, front-loaded with what you get and followed by the access condition; nothing is padded. The slight cost is that the first sentence's vague phrasing could be tightened rather than shortened.

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?

The tool is structurally simple (no params, no output schema), which lowers the bar. Still, with no output schema the description is the only place to explain what an agent actually receives back from "routes", and it omits that entirely.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No misleading parameter claims are made.

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 gives a verb and a resource ("See the available engine, marketplace and account routes"), so it is more than a restatement of the title. However, "routes" is unexplained domain jargon, and nothing distinguishes this from siblings like covenant_find or covenant_call – an agent cannot tell whether those also list routes or do something else.

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 account or key is needed to start" implies this is the entry-point/discovery tool, which is a usable usage cue. But the guidance is implicit: there is no explicit "call this first" instruction, no when-not-to-use, and no reference to any alternative tool.

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