Skip to main content
Glama

l402_inspect

Decode an L402 macaroon to reveal its identifier and caveats, helping you verify and inspect payment credentials before use.

Instructions

Decode an L402 macaroon and show its identifier and caveats.

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": {
      "macaroon": "<macaroon>"
    },
    "name": "l402_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
macaroonYesThe macaroon string to inspect

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. It implies a read-only decode operation but does not state that it performs no verification or mutation, nor does it describe behavior for malformed macaroons, permissions, or errors.

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?

The definition is a single front-loaded sentence with no wasted wording. It could be slightly more informative about the decode operation, but its brevity is appropriate for a one-parameter utility.

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 simple one-parameter read tool, the description is minimally adequate: it names the input and the returned fields. However, without an output schema or annotations, it omits important details such as whether the macaroon is validated or how errors are surfaced.

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 the single parameter is clearly documented as 'The macaroon string to inspect.' The description adds little beyond the schema, so the baseline of 3 is appropriate.

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 specific verb and resource ('Decode an L402 macaroon') and even names the return contents ('identifier and caveats'). It is clear what the tool does, but it does not distinguish itself from siblings such as l402_check or explain how decoding differs from verification.

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 guidance on when to use this tool versus alternatives like l402_check or l402_request. The description gives no preconditions, exclusions, or context that would help an agent choose it correctly.

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