Skip to main content
Glama

Puesto directory

puesto_directory
Read-onlyIdempotent

Free sample: https://apexfaucet.xyz/p/index.json?q=cafe ($0.002). Search live Mi Puesto pages in Gran Canaria. Does not create a page or take a payment. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
qNooptional search words, at most 60 characters
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the description only needs to add context. It does add real value: the $0.002 per-call price, the x402 payment currencies (USDC on Arc/Base/Solana, XNT on X1), and the fact that passing `payment` completes the purchase inside the call. The claim 'Does not ... take a payment' sits awkwardly beside the per-call charge, which leaves a small ambiguity about what is actually being paid for.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The sentence order is backwards: the free-sample URL leads, the actual purpose appears second, and the price is stated twice. Every element is useful, but the duplication and the promotional opener make it slower to parse than necessary.

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?

With no output schema, the description should say enough about results and access cost, and it does: it names the data source, the price, and the free sample endpoint an agent can fetch to inspect result shape. What remains unstated is result format or pagination, but for a two-optional-parameter search tool this is close to complete.

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?

Schema coverage is 100%, so both parameters are already documented. The description still adds meaning beyond the schema by explaining the stateful use of `payment` (fetch terms first, sign, then resubmit) and by showing `q` in action via the sample URL '?q=cafe'.

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 gives a specific verb and resource: 'Search live Mi Puesto pages in Gran Canaria', and it explicitly rules out adjacent actions ('Does not create a page'). It is clearly distinguishable from a generic directory-search tool, though the promotional 'Free sample:' opener competes with the purpose statement for the reader's attention.

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 an explicit two-step protocol: call once without `payment` to obtain terms, sign with your own wallet, then call again with `payment`. It also states a negative boundary (does not create a page or take a payment for a listing). It does not name any sibling search tool as an alternative, so routing among the many other search tools is left implicit.

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