Skip to main content
Glama

arobi_authorize

Decide whether an agent action is permitted under a sealed route grant, then seal a hash-chained authorization record with GRANTED, DENIED, or ESCALATED status and reason code.

Instructions

Decide whether an agent action is permitted against a sealed route grant, and seal a hash-chained AUTHORIZATION record. Returns GRANTED, DENIED, or ESCALATED with checks and reason code.

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_grant": "<route_grant>",
      "action": "<action>",
      "consequence_tier": "<consequence_tier>",
      "principal": "<principal>"
    },
    "name": "arobi_authorize"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction name, e.g. issue.refund
principalYesWho is acting.
auth_methodNoHow the principal authenticated, e.g. webauthn.
route_grantYesThe route_grant object returned by arobi_route_grant.
transactionNoOptional action context: resource, amount, category, payee.
consequence_tierYesImpact tier of the proposed action.
auth_freshness_secNoAge in seconds of that authentication.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 burden. It usefully discloses the three possible outcomes (GRANTED, DENIED, ESCALATED) and the write side effect of sealing a hash-chained record, which is meaningful for a decision tool. It does not say whether a record is sealed even on DENIED, whether calls are idempotent, or what escalation obligates the caller to do.

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 with zero filler: the decision is front-loaded and the return contract follows immediately. Nothing is repeated from the title or schema.

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 authorization tool with no output schema, the description does cover the return vocabulary, which is the most important gap it could have filled. However, the semantics of ESCALATED, the consequences of the hash-chained write, and failure behavior remain unaddressed.

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% and every parameter, including the consequence_tier enum, is documented in the schema, so the baseline is 3. The description adds the framing of route_grant as 'sealed' but no additional syntax, format, or default information beyond the schema.

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: decides whether an action is permitted against a sealed route grant, and additionally seals an AUTHORIZATION record. That is far more informative than the name alone. It stops short of explicitly differentiating itself from siblings such as arobi_route_grant or arobi_verify_chain, though the 'sealed route grant' input implies the sequencing.

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 implied rather than stated: the tool operates on a route_grant 'returned by arobi_route_grant', which conveys a prerequisite without saying so directly. There is no explicit when-to-use/when-not guidance and no statement of what to do when the result is ESCALATED versus DENIED.

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