Skip to main content
Glama

get_day_pass

Day Pass: one $0.25 payment (x402, USDC Base) unlocks 24h of unlimited calls on every micro route. Buy once via tools/call settle, then send the returned dp_ token as X-DAY-PASS header. For agents making 20+ calls/day.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_day_pass"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses price, payment rail (x402/USDC Base), duration, coverage, purchase mechanism, and auth header format. It leaves unclear what this specific no-param call returns and what happens at expiry or on failed payment, so it is strong but not complete.

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 compact sentences front-load the product, price, and scope, then give the buy/header flow and the usage threshold. It has no redundant filler.

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 payment/pass tool with no annotations and no output schema, the description covers cost, payment method, token usage, and target user well. However, it does not clarify whether get_day_pass returns pass details, initiates payment, or merely documents a separate settle call, leaving a material gap for correct invocation.

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

Parameters4/5

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

The tool has zero parameters and an empty schema, so there is no parameter meaning to add; baseline 4 applies. The description's mention of the dp_ token is auth-flow context, not an input parameter.

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 names the Day Pass product, its $0.25 cost, 24h unlimited scope across micro routes, and the high-volume agent threshold, so the offering is distinguishable from sibling utility tools. It stops short of stating explicitly what invoking get_day_pass itself does versus the separate settle call, so it is not 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 Guidelines4/5

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

It gives a clear use condition ('20+ calls/day') and outlines the purchase flow (settle then send X-DAY-PASS header). It does not name when not to use it or compare against pay-per-call alternatives beyond the implied threshold.

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.

Resources