Skip to main content
Glama

discover_verified_stores

[EN] Query ERC-8004 Dual-Tier AI Marketplace (INSTITUTIONAL_B2B & RETAIL_INDIE) across 8 verticals, including Official First-Party curated packages. | [ES] Consulta el Catálogo Dual ERC-8004 (Institucional B2B y Retail/Indie) en las 8 verticales y paquetes oficiales. | [中文] 查询 ERC-8004 双层 AI 市场目录(机构 B2B 与零售/独立开发者,覆盖 8 大垂直领域)。

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

Input Schema

NameRequiredDescriptionDefault
verticalNoFilter by vertical (e.g. VERTICAL_1_DATASET, VERTICAL_2_QUANT_ALPHA, VERTICAL_3_SOLIDITY_SECURITY, etc. or ALL).
marketTierNoFilter by INSTITUTIONAL_B2B (non-retail enterprise/funds), RETAIL_INDIE (traders/indie bots), or ALL.
maxPriceUsdcNoOptional maximum starting price in USDC.
minReputationNoMinimum ERC-8004 reputation score (0-100). Recommended >= 70.
firstPartyOnlyNoIf true, returns only TrustGate Official First-Party stores & instant-delivery bundles.
callerSectorOrTrendNoOptional: specify your project's industry sector or your user's shopping/search trend to personalize recommendations and VIP discounts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / callerSectorOrTrend
      Added value: +{
      +  "description": "Optional: specify your project's industry sector or your user's shopping/search trend to personalize recommendations and VIP discounts.",
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.9/5.0
Behavior3/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. The verb 'Query' implies a read-only operation, and the description discloses the marketplace tiers, 8 verticals, and first-party package coverage, but it omits permissions, result limits, pagination, sorting, and what a returned 'store' contains.

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

Conciseness2/5

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

The same catalog description is repeated three times in English, Spanish, and Chinese, which triples length without adding information for an agent that can read the English version. The English text is front-loaded, but the redundant translations make the definition unnecessarily bloated.

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 six-parameter discovery tool with no annotations and no output schema, the description covers the catalog scope and vertical/tier concepts adequately. However, it does not explain return structure, result limits, pagination, or how personalization and VIP discounts affect results, leaving meaningful operational gaps.

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 description coverage is 100%, so the schema already explains all six optional filters. The description reinforces the vertical and market-tier concepts but adds no syntax, default behavior, interaction between filters, or meaning beyond what the structured schema provides.

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 states a specific verb and resource: querying the ERC-8004 Dual-Tier AI Marketplace across 8 verticals, including Official First-Party curated packages. This is clear enough to distinguish a discovery/catalog tool from sibling actions like purchase or register, but it does not explicitly name or contrast those alternatives.

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

Usage Guidelines2/5

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

It implies the tool is for browsing or querying the marketplace, but gives no explicit guidance on when to use it versus purchase_firstparty_catalog_item, register_and_certify_store, or other siblings. There are no when-not-to-use conditions, prerequisites, or recommended workflows.

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.