Skip to main content
Glama

l402_check

Probes a URL to detect L402 protection and reports the invoice price and macaroon caveats when present, so agents can decide whether payment is required.

Instructions

Probe a URL to see whether it is L402-protected, and report the invoice price and macaroon caveats when present.

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": {
      "url": "<url>"
    },
    "name": "l402_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to probe

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 behavioral burden. It does disclose the diagnostic payload (protection status, invoice price, macaroon caveats), which is genuine added value. It is silent, however, on what the probe actually does on the wire – whether it fetches the resource, whether merrily probing could consume or pay an L402 offer, and what is returned for a non-protected URL.

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?

One sentence, front-loaded with the action and the URL, followed immediately by what is reported. Every clause earns its place and there is no redundant restatement of the tool name.

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?

With no output schema, the description must convey return shape, and it does so only loosely – it names two fields but not the overall structure or the non-protected case. For a simple one-parameter probe this is adequate but leaves real gaps an agent would want filled.

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?

There is a single parameter with 100% schema description coverage ("The URL to probe"), so the schema already does the work. The description adds no format, scheme, or constraint detail beyond it, making the baseline 3 correct.

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 ("Probe") on a specific resource (a URL) and states the outcome: whether it is L402-protected, plus invoice price and macaroon caveats. That is far more informative than the bare tool name. It does not, however, distinguish itself from closely related siblings such as l402_inspect or l402_request, so it stops short of a 5.

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: an agent can infer this is the discovery step before paying or requesting, but the description never states when to choose it over l402_inspect or l402_request, nor when not to use it. There are no prerequisites or exclusions offered.

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