Skip to main content
Glama

Arobi Immaculate MCP

arobi_route_grant

Seal WHO granted WHAT authority to WHICH workflow, with scope, caps, attenuation and expiry. One grant authorises many later arobi_authorize decisions.

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": {
      "route_id": "<route_id>",
      "scope": "<scope>",
      "granted_by": "<granted_by>",
      "delegated_to": "<delegated_to>"
    },
    "name": "arobi_route_grant"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeYes{ actions: string[], category_caps?: Record<string, number> }
route_idYes
revocableNo
expires_atNoISO 8601.
granted_byYes
attenuationNoPlain-language limits carried with the grant.
delegated_toYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. "Seal" plus "One grant authorises many later arobi_authorize decisions" usefully conveys that this writes durable, reusable authorization state with built-in attenuation and expiry. However, it does not say whether sealing is irreversible, what happens if a grant already exists for the same route, what permissions the caller needs, or what the operation returns.

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 tightly packed sentences with the core identity front-loaded and the sibling relationship as a follow-on clause; nothing is filler. The all-caps WHO/WHAT/WHICH is a stylistic flourish that slightly hurts readability but does reinforce the key fields.

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 7-parameter, nested-object mutation tool with no annotations and no output schema, the definition covers the conceptual model but leaves gaps: no indication of return value (grant identifier for later reference/revocation), no conflict or idempotency behavior, and no coverage of the two undocumented parameters.

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 description coverage is only 43% across 7 parameters, and the prose covers the conceptual roles of granted_by, scope, attenuation and expiry (caps are named inside scope). It does not disambiguate route_id from delegated_to — the two identifiers most likely to be confused — and never explains the revocable flag or the expected shape of the nested scope object beyond what the schema already shows.

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 concrete action ("seal" a grant of authority) and enumerates the elements being recorded — grantor, scope, workflow, caps, attenuation, expiry — which maps cleanly onto the tool name. It also explicitly separates this tool from arobi_authorize by framing a grant as authorising many later authorize decisions. The verb "seal" is somewhat metaphorical, but the intent is still recoverable.

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 only implied: the second sentence tells the agent a grant precedes and covers many arobi_authorize calls, which suggests creating a grant up front rather than per-call. There is no explicit when-not-to-use guidance, no statement of prerequisites (who may seal a grant, whether the route must already exist), and no mention of revoking or superseding an existing grant.

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.