Skip to main content
Glama

find_marketplace_products

Find and rank live data APIs by describing your desired outcome, then preview and pay only for the best match.

Instructions

Free discovery tool. Rank the live DopamineDesk x402 catalog against a plain-language buyer task before choosing or paying for a product.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesPlain-language task or desired outcome, such as "verify a vendor before onboarding" or "check a Base transaction receipt".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.11.3

TDQS

A4.8/5.0
Behavior4/5

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

Since no annotations are provided, the description must convey behavioral traits. It states 'Free discovery tool' and 'before choosing or paying,' which strongly implies a read-only, non-destructive operation. However, it does not detail what happens after ranking or any potential side effects, leaving a slight gap.

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?

The description is a single, compact sentence that front-loads the key information ('Free discovery tool') and states the action and purpose without any redundant wording. It is efficient and easy to parse.

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?

Given the simplicity of the tool (one parameter, no output schema) and the presence of a sibling purchase tool, the description provides all necessary context. It explains what the tool does, when to use it, and what input is required, fully covering the use case.

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

Parameters5/5

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

The single required parameter 'query' is well-defined with a clear description: 'Plain-language task or desired outcome, such as ...' This directly aligns with the tool's purpose and gives concrete examples, making the input unambiguous.

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 clearly states the tool's function: to rank the live DopamineDesk x402 catalog against a plain-language buyer task. It specifies the action (rank), resource (catalog), and context (before choosing or paying). This distinctly separates it from the sibling purchase tool.

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?

The description explicitly indicates when to use this tool: 'before choosing or paying for a product.' This implies it should precede the purchase_marketplace_product tool. The phrase 'Free discovery tool' also signals it is a low-risk, preliminary step.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.