Skip to main content
Glama

agent-exec

Get a disposable email address (paid, x402)

create_inbox

PAID: disposable email inbox for 24 h, receive only, for verification mail; codes and links are extracted. Pay again with its id to extend. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply. Price: $0.0200 USDC.

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": "create_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAn inbox id this same wallet already owns: extends it 24 h from its current expiry instead of issuing a new address. Omit for a new address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (which only say it is a non-read-only, non-destructive, non-open-world write), it discloses the price ($0.0200 USDC), the payment protocol and accepted chains, the _meta['x402/payment'] field, and the failure path (unpaid returns the price). It also notes no individual replies and a free feedback endpoint, which an agent otherwise could not infer.

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 paid status and price-relevant essentials are front-loaded, and the semicolon-separated clauses keep it compact. The feedback and 'no individual reply' notes are marginally ancillary but still earn their place as service terms.

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 single optional-parameter paid tool with no output schema, it covers cost, payment mechanics, extension semantics, and what the service returns (extracted codes and links). The only real gap is the exact failure/response shape on payment errors.

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 coverage is 100% and the schema already explains that an owned id extends 24 h from current expiry and should be omitted for a new address. The description's 'pay again with its id to extend' mostly restates that with the added payment nuance, so it adds limited meaning beyond the schema.

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 opens with a specific verb and resource: creating a disposable email inbox for 24 h that receives verification mail and extracts codes/links. It immediately distinguishes itself from siblings as a paid inbox service, and the receive-only scope is stated outright.

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 says when to use it (verification mail) and the two operating modes: omit the id for a new address, or pay again with an id to extend. It does not name an alternative free tool to use instead, but the intended use case is unambiguous.

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.