Skip to main content
Glama

Find a service to buy

search_services
Read-onlyIdempotent

Find purchasable outcomes by words, budget and readiness across x402, escrow and prepaid calls. Returns operator, exact price with fee, input and result examples, availability and the next free quote request. Requires no account or payment. Use search_agents for identity discovery and authenticated plan_work for a personalized plan. Free.

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

Input Schema

NameRequiredDescriptionDefault
qNoWords describing the outcome, e.g. metadata.
modeNoOnly offers bought this way: platform or seller x402 call, x402 work order, reusable escrow, prepaid instant or manual escrow.
pageNoResult page, starting at 1 (default 1).
sortNoResult order: relevance, newest, or buyer total price ascending or descending.relevance
limitNoOffers per page, 1 to 50 (default 20).
orderableNoWhen true, only offers that can be bought now (seller worker online and capacity free).
max_total_usdNoAll-in USD ceiling, before separate wallet network costs.

Output Schema

NameRequiredDescriptionDefault
pageYes
limitYes
totalYes
offersYes
has_moreYes
inventoryYes
observed_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new context: no account, no payment, free to call, and what each result carries (operator, exact price with fee, examples, availability, next free quote request). It stops short of anything about rate limits or result-set behavior, but the cost/access disclosure is the highest-value item and it is present.

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?

Three tight sentences, front-loaded with what the tool finds and what it returns, then routing, then access terms. The trailing 'Free.' slightly duplicates the earlier 'Requires no account or payment', which is the one piece of marginal wording in an otherwise dense description.

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?

An output schema exists, so return shapes need not be spelled out, yet the description still summarizes the payload, plus access requirements (no account, no payment) and sibling routing. For a 7-parameter, no-required-arg discovery tool this covers everything an agent needs to call it correctly.

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 baseline is 3, but the description adds a useful conceptual mapping — 'words, budget and readiness' corresponds to q, max_total_usd and orderable — which tells an agent how to think about filtering rather than just which fields exist. It does not add syntax or format details beyond the schema, so it is above baseline without being exhaustive.

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?

States a specific verb and resource ('Find purchasable outcomes') plus the scoping axes (words, budget, readiness) and the payment rails covered (x402, escrow, prepaid). It explicitly separates itself from search_agents (identity discovery) and plan_work (personalized plan), so an agent can route without opening either schema.

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?

Names two alternatives with the conditions that select them: search_agents for identity discovery, authenticated plan_work for a personalized plan. It also signals the intended entry scenario (searching by outcome words, budget ceiling and buy-now readiness). Little is left to inference about when this tool is the right pick.

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