Skip to main content
Glama

search_merchants

Resolve public prepared-artifact resources by provider-agent name or active resource text, newest-created first (offer ID ascending breaks ties). Returns current versions, formats, prices, and checkout references; does not execute tasks or require a merchant ID or bearer key.

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_merchants"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoAt most 80 UTF-16 code units after trimming; a non-BMP character such as an emoji counts as two.
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / query / description
      Added value: +"At most 80 UTF-16 code units after trimming; a non-BMP character such as an emoji counts as two."
    • addedInput schema / properties / query / x-maxUtf16CodeUnits
      Added value: +80
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden and does well: it discloses result ordering (newest-created first, offer ID ascending as tiebreak), what the records contain, and that no merchant ID or bearer key is needed. It omits pagination behavior, rate limits, and whether omitted query params widen the result set.

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?

Two dense sentences, front-loaded with the core action and ordering before the return-value and non-execution clauses. Every clause adds information, though the parenthetical tiebreak detail could be trimmed for an agent that only needs selection cues.

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 3-parameter, annotation-free, no-output-schema tool, the description covers returns and access requirements but leaves key gaps: nothing explains what an empty query returns (0 required params), nor how limit/cursor behave. Adequate to call correctly in the common case, incomplete for paginated or unfiltered use.

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 33%: only query is documented in the schema, and the description usefully clarifies its two accepted forms (provider-agent name or active resource text). But limit and cursor receive no explanation anywhere, so an agent gets no guidance on page size defaults or how the cursor value relates to the stated ordering.

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?

States a specific verb and resource: resolve public prepared-artifact resources, keyed by provider-agent name or active resource text, with declared ordering. It also distinguishes itself from the purchase path by saying it does not execute tasks. Minor friction: the tool name says 'merchants' while the description is about artifacts/offers, so an agent must reconcile the two.

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

Usage Guidelines3/5

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

The clause 'does not execute tasks or require a merchant ID or bearer key' implicitly frames this as the unauthenticated discovery step before buy_prepared_artifact, which is useful when-not context. However, it never explicitly names a sibling alternative (e.g. discover_merchant_offers) or states the conditions under which that would be preferred, leaving routing to inference.

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