Skip to main content
Glama

Arobi Immaculate MCP

arobi_authorize

Decide whether an agent action is permitted against a sealed route grant, and seal an AUTHORIZATION record. Returns GRANTED, DENIED or ESCALATED with the reason. Call arobi_route_grant first to obtain the grant.

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.
transactionNoAction context: resource, amount, category, payee.
consequence_tierYes
auth_freshness_secNoAge in seconds of that authentication.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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: it does disclose that the call seals a persistent record and returns one of three verdicts with a reason, which is real behavioral signal. However, it says nothing about idempotency, irreversibility of the sealed record, authentication requirements (auth_method, auth_freshness_sec), or what the caller should do on DENIED/ESCALATED.

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?

Three short sentences, front-loaded with the decision and side effect, then the return values, then the prerequisite. No filler or restatement of the title.

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?

For a 7-parameter tool with a nested object and no output schema, the description helpfully names the return values and the required prior call. It is slightly thin on the escalation path and on what 'seal' implies for the caller, but nothing essential to invoking it correctly is missing.

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 86%, so the input schema already documents nearly every parameter, including the route_grant origin and the auth fields. The description adds no syntax, format, or threshold 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb-plus-resource statement: it decides an authorization against a sealed route grant and writes an AUTHORIZATION record. It also names the possible verdicts (GRANTED, DENIED, ESCALATED), which distinguishes it from the sibling arobi_route_grant that merely issues the grant.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The prerequisite is explicit: 'Call arobi_route_grant first to obtain the grant,' which tells the agent the correct ordering relative to a sibling. It stops short of stating when not to use this tool or how to handle an ESCALATED result, so it is strong context without full exclusion guidance.

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.