Skip to main content
Glama
Sign In

CAN-TAP Verified

by io.github.morphious33453
OverviewDiscussionsAdmin

claim_listing

Claim a free verified directory listing for a Canadian business — receives a permanent dofollow backlink upon domain ownership verification. Use this when a user wants to add their business to the CAN-TAP Verified directory. Rate-limited to 5 claims per IP per day.

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": {
      "business_name": "<business_name>",
      "website": "<website>",
      "city": "<city>",
      "province": "<province>",
      "email": "<email>"
    },
    "name": "claim_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesPrimary city the business serves
emailYesBusiness email address (must match website domain for fast verification)
phoneNoBusiness phone number (optional)
tradeNoBusiness trade/category (optional)
websiteYesFull URL of the business website (https://...)
provinceYesTwo-letter Canadian province code
business_nameYesLegal or trading name of the business
google_review_linkNoOptional Google review URL — used for the NFC tap-to-review system

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the transparency burden. It discloses key behaviors: the listing is free, verified, earns a permanent dofollow backlink after domain ownership verification, and is rate-limited to 5 claims per IP per day. This is meaningful operational context, though it does not describe failure modes or response behavior.

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 two sentences, front-loaded with the core purpose and then adding rate-limit and verification context. Every sentence contributes useful information with no redundancy.

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 moderately complex tool with 8 parameters and no output schema, the description covers the key context: when to use it, the rate limit, and the verification requirement for the permanent backlink. It omits return-value details, but the selection decision is well supported.

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?

All 8 parameters have schema descriptions (100% coverage), so the schema already provides parameter semantics. The description does not add additional detail about specific parameters beyond the schema, so it earns the baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Claim') and resource ('free verified directory listing') and states exactly what the tool accomplishes. It also explicitly says 'Use this when a user wants to add their business to the CAN-TAP Verified directory,' which clearly distinguishes it from sibling tools like check_backlink_status and search_directory.

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?

The description provides a clear use case: add a business to the CAN-TAP Verified directory. It does not mention when not to use it or name alternatives, but the input context and sibling names make the appropriate usage evident.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CAN-TAP Verified toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources