Skip to main content
Glama

veritas-8183-3star-rating-seal

discover_verified_stores

Read-onlyIdempotent

[Public registry] Find AI data, code and model sellers that already passed an audit, filtered by trust score, category or max price. Example: minReputation=85, vertical='VERTICAL_3_SOLIDITY_SECURITY'.

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
verticalNoAudit vertical category to filter providers.
marketTierNoTarget market lane to filter stores and packages.
maxPriceUsdcNoMaximum starting price in USDC.
minReputationNoMinimum ERC-8004 reputation score (0 to 100).
firstPartyOnlyNoReturn only official TrustGate curated packages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedInput schema / properties / callerSectorOrTrend
      Removed value: -{
      -  "description": "Optional: specify your project's industry sector or your user's shopping/search trend to personalize recommendations and VIP discounts.",
      -  "type": "string"
      -}
    • changedInput schema / properties / firstPartyOnly / description
      Previous value: -"If true, returns only TrustGate Official First-Party stores & instant-delivery bundles."New value: +"Return only official TrustGate curated packages."
    • changedInput schema / properties / marketTier / description
      Previous value: -"Filter by INSTITUTIONAL_B2B (non-retail enterprise/funds), RETAIL_INDIE (traders/indie bots), or ALL."New value: +"Target market lane to filter stores and packages."
    • changedInput schema / properties / maxPriceUsdc / description
      Previous value: -"Optional maximum starting price in USDC."New value: +"Maximum starting price in USDC."
    • changedInput schema / properties / minReputation / description
      Previous value: -"Minimum ERC-8004 reputation score (0-100). Recommended >= 70."New value: +"Minimum ERC-8004 reputation score (0 to 100)."
    • addedInput schema / properties / minReputation / examples
      Added value: +[
      +  85
      +]
    • changedInput schema / properties / vertical / description
      Previous value: -"Filter by vertical (e.g. VERTICAL_1_DATASET, VERTICAL_2_QUANT_ALPHA, VERTICAL_3_SOLIDITY_SECURITY, etc. or ALL)."New value: +"Audit vertical category to filter providers."
    • addedInput schema / properties / vertical / enum
      Added value: +[
      +  "ALL",
      +  "VERTICAL_1_DATASET",
      +  "VERTICAL_2_QUANT_ALPHA",
      +  "VERTICAL_3_SOLIDITY_SECURITY",
      +  "VERTICAL_4_X402_ORACLES",
      +  "VERTICAL_5_CERTIFIED_SKILLS",
      +  "VERTICAL_6_RAG_KNOWLEDGE",
      +  "VERTICAL_7_VERIFIED_INFERENCE",
      +  "VERTICAL_8_DEPIN_GPU"
      +]
  2. 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"
      +}
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds two genuinely useful behavioral facts beyond that: results come only from the public registry and only from sellers that already passed an audit. It stops short of noting result limits, ordering, or pagination.

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 sentences, zero preamble, with the scoping tag and the core action front-loaded before the filter list. The example is compact and combined-filter rather than a restatement, though it partly duplicates the schema's own examples.

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 five optional parameters, no required inputs, and no output schema, the description gives enough to call it correctly and to interpret the trust/vertical/price parameters in combination. The main remaining gap is that nothing describes the shape of the returned results, which matters for a discovery tool with no output schema.

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% and includes an example for minReputation, so the schema carries the parameter burden. The description's example combining minReputation=85 with vertical='VERTICAL_3_SOLIDITY_SECURITY' illustrates how filters compose, which is marginal added value over the per-field descriptions, so the baseline of 3 applies.

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?

Specific verb and resource: "Find AI data, code and model sellers that already passed an audit," scoped by "[Public registry]." The supply-side (seller) framing plus the pre-audited qualifier distinguishes it from the buyer-side sibling match_verified_buyers_by_intent and from register_and_certify_store, though it never names those alternatives explicitly.

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?

Usage is implied by the filterable dimensions (trust score, category, max price) and the worked example, so an agent can infer this is the discovery/browse entry point. However, there is no explicit when-to-use vs when-not, no statement of prerequisites, and no routing to audit_* tools for sellers that have not yet passed an audit.

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.