Skip to main content
Glama

Agent Control — Agent Meter

by net.agent-control
OverviewDiscussionsAdmin

Buy an Agent Meter pass

meter_buy_pass

Can I pay this address? Buy looks_20 pack ($0.20) or look $0.10. Stamp ticket $0.05. No inbox. Call with sku looks_20 (or omit) to buy a pack that mints/extends X-Agent-Pass. look $0.10 is optional one-shot. Returns a payable invoice as tool content (ok:true / status payment_required) with pay_to, base_pay_to, accepts (Base USDC EIP-3009 exact and Solana USDC), amount_usd, amount_base_units, reference, pay_url, invoice_id, watch_url, adapter_url, base_adapter_url, preferred_rail, pay_page, next_tool, tool_fields, sign_exact, adapter_snippet, next_steps. Prefer Base EIP-3009 exact to base_pay_to (CDP/AgentKit; no Solana key) then meter_watch with payment. Use sign_exact + adapter_snippet to finish in-process (payMeterPassBase / signTypedData). Fetch base_adapter_url only if you need the full file. Optional Solana: fetch adapter_url. 402 invoice includes pay_page for Phantom laptop as a last resort. We never take keys. Packs: looks_20 / addresses_100 / stamp_tx. No human account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skuNoCatalog id from meter_pricing. Omit or looks_20 is the paid pack. look $0.10 is optional one-shot. Packs: looks_20, addresses_100, stamp_tx. pass_1h stays in catalog only.
proofNoPayment proof. { type: dev } only when METER_DEV_GRANT=1. Never send a secret key.
paymentNoOptional Base EIP-3009 exact payload. Same JSON as PAYMENT-SIGNATURE. Never send a secret key.
signatureNoOptional on-chain tx signature after you sign locally. Not a private key.
pass_tokenNoExisting X-Agent-Pass to extend with a pack.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sku / description
      Previous value: -"Catalog id from meter_pricing. Omit or looks_20 is the pack after free-5. look $0.10 is optional one-shot. Packs: looks_20, addresses_100, stamp_tx. pass_1h stays in catalog only."New value: +"Catalog id from meter_pricing. Omit or looks_20 is the paid pack. look $0.10 is optional one-shot. Packs: looks_20, addresses_100, stamp_tx. pass_1h stays in catalog only."
  2. Changed1 schema field changed
    • changedInput schema / properties / sku / description
      Previous value: -"Catalog id from meter_pricing. Omit or looks_20 is the pack after 5 free. sku look is $0.10 one-shot. Packs: looks_20, addresses_100, stamp_tx. pass_1h stays in catalog only."New value: +"Catalog id from meter_pricing. Omit or looks_20 is the pack after free-5. look $0.10 is optional one-shot. Packs: looks_20, addresses_100, stamp_tx. pass_1h stays in catalog only."
  3. Changed3 schema fields changed
    • addedInput schema / properties / pass_token / description
      Added value: +"Existing X-Agent-Pass to extend with a pack."
    • addedInput schema / properties / payment
      Added value: +{
+  "description": "Optional Base EIP-3009 exact payload. Same JSON as PAYMENT-SIGNATURE. Never send a secret key.",
+  "type": "object"
+}
    • changedInput schema / properties / sku / description
      Previous value: -"Catalog id from meter_pricing. Default look (current door). Packs: looks_20, addresses_100, stamp_tx. pass_1h stays in catalog only."New value: +"Catalog id from meter_pricing. Omit or looks_20 is the pack after 5 free. sku look is $0.10 one-shot. Packs: looks_20, addresses_100, stamp_tx. pass_1h stays in catalog only."
  4. Changed3 schema fields changed
    • changedInput schema / properties / proof / description
      Previous value: -"Payment proof. { type: dev } only when METER_DEV_GRANT=1"New value: +"Payment proof. { type: dev } only when METER_DEV_GRANT=1. Never send a secret key."
    • addedInput schema / properties / signature
      Added value: +{
+  "description": "Optional on-chain tx signature after you sign locally. Not a private key.",
+  "type": "string"
+}
    • changedInput schema / properties / sku / description
      Previous value: -"look (default $0.02), looks_20 ($0.20), addresses_100 ($0.15), stamp_tx ($0.05). pass_1h stays in catalog only."New value: +"Catalog id from meter_pricing. Default look (current door). Packs: looks_20, addresses_100, stamp_tx. pass_1h stays in catalog only."
  5. Changed1 schema field changed
    • changedInput schema / properties / sku / description
      Previous value: -"pass_1h (default $0.25), pass_24h, calls_1k, stamp_tx, or scan_batch"New value: +"look (default $0.02), looks_20 ($0.20), addresses_100 ($0.15), stamp_tx ($0.05). pass_1h stays in catalog only."
  6. Changed1 schema field changed
    • changedInput schema / properties / sku / description
      Previous value: -"pass_1h"New value: +"pass_1h (default $0.25), pass_24h, calls_1k, stamp_tx, or scan_batch"
  7. Added

TDQS

A4.9/5.0
Behavior5/5

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

Despite minimal annotations (readOnlyHint=false, destructiveHint=false), the description fully discloses the tool's behavior: it returns a payable invoice with a detailed field list, states 'No inbox' and 'We never take keys,' and explains the security posture. It also covers the payment rails and response statuses, far exceeding the annotation baseline.

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 description is dense and information-rich, but it is logically structured with an opening that clarifies the core purpose and price points, followed by payment rails, response fields, and security notes. Every sentence contributes value, though the long list of invoice fields could be visually streamlined. It remains readable and well-organized.

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

Completeness5/5

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

Given the complexity of a payment tool with multiple rails, response fields, and next-step instructions, the description is remarkably complete. It covers the return format, how to use the returned fields, integration with meter_watch, security considerations, and edge cases like the 402 pay_page fallback. Without an output schema, it compensates fully.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds substantial meaning beyond the schema. For instance, it explains the sku options, when proof is allowed (only with METER_DEV_GRANT=1), the nature of the payment payload, and the pass_token usage for extension. This enriches each parameter with practical context the schema alone lacks.

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?

The description clearly states the action (buy) and the resource (Agent Meter pass), with specific pack names and prices. It distinguishes itself from siblings like meter_pricing by focusing on the purchase and mint/extend action, and it names the exact SKUs and their purposes.

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

Usage Guidelines5/5

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

It provides explicit usage instructions: 'Prefer Base EIP-3009 exact to base_pay_to (CDP/AgentKit; no Solana key) then meter_watch with payment,' and explains when to fetch adapter_url, how to finish in-process, and when to use pay_page as a last resort. This clearly routes the agent to the correct alternative tools and payment flow.

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

All Agent Control — Agent Meter toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources