Skip to main content
Glama

arobi_route_grant

Seal delegated workflow authority with scoped actions, category caps, attenuation, and expiry, then return an Ed25519-signed grant and hash-chained record.

Instructions

Seal WHO granted WHAT authority to WHICH workflow, with scope, category caps, attenuation, and expiry. Returns a locally Ed25519-signed route_grant and hash-chained ROUTE_GRANT record.

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
scopeYesAllowed actions and optional per-category spending caps.
route_idYesUnique identifier for this workflow route.
revocableNoWhether the grant can be revoked (default true).
expires_atNoISO 8601 expiry timestamp (defaults to +24h).
granted_byYesPrincipal issuing the authority grant.
attenuationNoPlain-language limits carried with the grant.
delegated_toYesAgent or workflow receiving delegated authority.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 it does disclose meaningful behavior: the tool returns a locally Ed25519-signed route_grant plus a hash-chained ROUTE_GRANT record, implying an append-only audit trail. However, it omits what an agent most needs for a mutation: whether 'seal' means the grant is immutable, what happens if route_id already exists, required caller identity or auth, and whether the operation is idempotent.

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?

Two sentences, front-loaded with the WHO/WHAT/WHICH framing that maps directly to the required parameters, then the return artifacts. No filler, no repetition of the schema.

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

Completeness4/5

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

With no output schema, the description correctly takes on the return-value explanation (signed grant plus hash-chained record), which is the most important missing structured information. For a 7-parameter nested mutation with no annotations, the remaining gaps are mutation semantics such as immutability, duplicate handling, and auth requirements, but the core picture is complete enough to call the tool.

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 100%, so the schema already documents all seven parameters, including the nested scope.actions and category_caps. The description names the same concepts (scope, caps, attenuation, expiry) but adds no format, default, or constraint detail beyond the schema, so the baseline of 3 applies.

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 uses a specific verb ('Seal') against a specific resource (a route grant binding granted_by, delegated_to, and route_id) and enumerates the dimensions it covers: scope, category caps, attenuation, and expiry. That is far more informative than the bare name. It stops short of distinguishing itself from the sibling arobi_authorize, which an agent may plausibly confuse with granting.

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 no when-to-use guidance, no prerequisites, and no mention of the alternatives. The reader must infer that this is the issuance step and that arobi_authorize or arobi_verify_chain handle the checking side. Nothing in the text excludes or redirects any case.

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