Skip to main content
Glama

register_and_certify_store

[EN] Freemium ERC-8004 Store Onboarding (0 USDC upfront; 2.0% Broker referral fee + 1.0%-1.5% Escrow fee on sales). Requires passing a live deterministic audit of sampleDeliverable for the target vertical. | [ES] Registro y certificación gratuita ERC-8004 para tiendas IA externas (auditoría determinista obligatoria en vivo; comisión solo por venta exitosa). | [中文] 免费注册并认证 ERC-8004 外部 AI 商店(0 预付费用,必须通过实时确定性安全审计,仅在成交时收取 2% 经纪佣金 + 托管费)。

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

Input Schema

NameRequiredDescriptionDefault
storeIdNo
verticalNo
storeNameNo
marketTierNo
endpointUrlNo
walletAddressNo
sampleDeliverableNoOptional sample deliverable payload to be audited live (if omitted, uses a verified reference template for 1-click onboarding).
startingPriceUsdcNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / sampleDeliverable / description
      Previous value: -"Sample deliverable payload to be audited live before listing."New value: +"Optional sample deliverable payload to be audited live (if omitted, uses a verified reference template for 1-click onboarding)."
    • removedInput schema / required
      Removed value: -[
      -  "storeId",
      -  "storeName",
      -  "walletAddress",
      -  "vertical",
      -  "sampleDeliverable"
      -]
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose genuinely useful behavior: zero upfront cost, success-only fee percentages, and a mandatory live deterministic audit before certification. It omits what happens on audit failure, whether registration is idempotent for a repeated storeId, and what artifact (certification, seal) the caller receives.

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 content is repeated verbatim in English, Spanish, and Chinese, tripling length without adding any information an agent can use; the [ES] and [中文] blocks restate the fee and audit facts already given. Front-loading is fine, but the redundancy is pure bloat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation with no annotations and no output schema, the description explains the commercial and audit context but leaves the mechanics thin: which fields are effectively required for onboarding, what the vertical and marketTier choices imply, and what the tool returns on success or audit failure are all unexplained.

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

Parameters2/5

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

Schema description coverage is only 13% — only sampleDeliverable is documented in the schema, and its optional/template fallback is echoed in the description. The other seven parameters (storeId, vertical, storeName, marketTier, endpointUrl, walletAddress, startingPriceUsdc) get no explanation in either place, so the description fails to compensate for the coverage gap on a non-trivial onboarding call.

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 [EN] segment states a concrete verb+resource pair: registering and certifying an external ERC-8004 store, with the fee model (0 upfront, 2.0% referral + 1.0%-1.5% escrow) and the audit gate. It is distinguishable from the audit_*_escrow siblings, which audit deals rather than onboard stores, though the description never names an alternative 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 rather than stated: an external AI store wanting to list must pass a live deterministic audit of sampleDeliverable for its vertical, and sampleDeliverable can be omitted for a 1-click template path. There is no explicit when-to-use versus when-not guidance, no mention of preconditions such as an existing wallet or required authorization, and no routing to discover_verified_stores or the audit tools.

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.