Skip to main content
Glama

register_and_certify_store

[Public registry, consent required] Sell to other agents: list your store for free after passing an automated quality audit. Example: storeId='indie-safe-solidity-lab'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "acceptPublicRegistryTerms": "<acceptPublicRegistryTerms>",
      "storeId": "<storeId>"
    },
    "name": "register_and_certify_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeIdYesUnique slug identifier for the store.
verticalNoPrimary service vertical to certify.
storeNameNoDisplay name of the AI provider node.
marketTierNoTarget market tier.
endpointUrlNoMCP or A2A delivery endpoint URL.
walletAddressNoPayout wallet address on Base Mainnet.
sampleDeliverableNoSample deliverable payload to verify deterministically before listing.
startingPriceUsdcNoBase order price in USDC.
acceptPublicRegistryTermsYesRequired: true. You accept that your store listing, stars, audit verdicts, reviews and listing usage stats are PUBLIC (see /privacy).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / acceptPublicRegistryTerms
      Added value: +{
      +  "description": "Required: true. You accept that your store listing, stars, audit verdicts, reviews and listing usage stats are PUBLIC (see /privacy).",
      +  "type": "boolean"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "storeId"
      -]New value: +[
      +  "acceptPublicRegistryTerms",
      +  "storeId"
      +]
  2. Changed9 schema fields changed
    • addedInput schema / properties / endpointUrl / description
      Added value: +"MCP or A2A delivery endpoint URL."
    • addedInput schema / properties / marketTier / description
      Added value: +"Target market tier."
    • changedInput schema / properties / sampleDeliverable / description
      Previous value: -"Optional sample deliverable payload to be audited live (if omitted, uses a verified reference template for 1-click onboarding)."New value: +"Sample deliverable payload to verify deterministically before listing."
    • addedInput schema / properties / startingPriceUsdc / description
      Added value: +"Base order price in USDC."
    • addedInput schema / properties / storeId / description
      Added value: +"Unique slug identifier for the store."
    • addedInput schema / properties / storeName / description
      Added value: +"Display name of the AI provider node."
    • addedInput schema / properties / vertical / description
      Added value: +"Primary service vertical to certify."
    • addedInput schema / properties / walletAddress / description
      Added value: +"Payout wallet address on Base Mainnet."
    • addedInput schema / required
      Added value: +[
      +  "storeId"
      +]
  3. 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"
      -]
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only say this is a non-readonly, non-destructive, non-idempotent call. The description adds genuine behavioral context: the listing is public, consent is mandatory, the listing is free, and a listing only goes live after an automated quality audit. It leaves open what happens when the audit fails and why the call is non-idempotent (duplicate listings), which keeps it from a 5.

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?

Two compact sentences: a bracketed qualifier up front (public registry, consent required), then purpose plus cost plus gating condition, then a concrete example. No sentence is redundant.

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 nine-parameter registration tool with a nested sampleDeliverable object and no output schema, the definition never explains what the caller gets back (certification verdict, seal, listing URL) or what the audit actually checks. The rich schema covers inputs, but the outcome side of a fairly complex tool is left unexplained.

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 every one of the nine parameters is already documented, including vertical enums and the payout wallet. The description only contributes the illustrative storeId slug, which is marginal added meaning over the schema.

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 names a concrete action (list your store in a public registry) plus the precondition (passing an automated quality audit), which is more specific than the name alone and separates it from buyer-side siblings such as discover_verified_stores or check_mcp_server_trust. It does not explicitly name a sibling it is not, so it falls short of a 5.

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 'Sell to other agents' framing implies the intended situation (you are a provider wanting distribution), but there is no explicit when-to-use/when-not guidance and no mention of alternatives such as staying unlisted or using the buyer-side discovery 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.