Skip to main content
Glama

Verify a listing as its vendor

verify_listing
Idempotent

For a vendor: prove a listing is theirs by a link to it or the Anchor badge on a page on their own domain or in their GitHub README. Use it only when your user runs the product. Never changes a grade.

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": {
      "slug": "<slug>",
      "url": "<url>"
    },
    "name": "verify_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe page with the badge or link, on the listing's own domain or its github.com README
slugYesThe listing's slug, page URL, or a package, GitHub owner/repo or registry name
dryRunNotrue: changes nothing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / dryRun
      Added value: +{
      +  "description": "true: changes nothing",
      +  "type": "boolean"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / slug / description
      Previous value: -"The listing, as a slug from search_tools (e.g. exa-mcp), its page's URL, or a package, GitHub owner/repo or MCP registry name it goes by"New value: +"The listing's slug, page URL, or a package, GitHub owner/repo or registry name"
    • changedInput schema / properties / url / description
      Previous value: -"The vendor's page with the badge or a link to the listing: on the listing's own domain, or the README of its repository on github.com"New value: +"The page with the badge or link, on the listing's own domain or its github.com README"
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already disclose that this is not read-only, is idempotent, is non-destructive, and operates in an open-world context. The description usefully adds that it never changes a grade and requires vendor/user-product eligibility, but it does not say what verification state is written or what success looks like.

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 three short sentences, front-loads the actor and action, and contains no filler. Each sentence contributes either the verification mechanism, the usage constraint, or the non-effect.

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?

For a three-parameter verification tool with full schema coverage, the description covers the actor, proof mechanism, eligibility condition, and one important behavioral limit. It could say more about the resulting verification state, but the annotations and schema carry most remaining context.

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 coverage is 100%, so the schema already documents the url, slug, and dryRun parameters in detail. The description reinforces the URL proof requirement but adds no new syntax, format, or edge-case guidance beyond 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 states a specific verb and resource: a vendor can prove a listing is theirs using a link or the Anchor badge. It gives the verification mechanism and scope, though it does not explicitly distinguish this tool from any named sibling.

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

Usage Guidelines4/5

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

It provides a clear eligibility rule: use it only when your user runs the product, and it frames the caller as a vendor. It does not name an alternative tool or explain what to use when the user does not run the product.

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.

Resources