Skip to main content
Glama
Sign In

CAN-TAP Verified

by io.github.morphious33453
OverviewDiscussionsAdmin

search_directory

Search the CAN-TAP Verified directory of 3,000+ real Canadian businesses by name, city, trade, or any combination. Returns matching listings with their URLs and claim status.

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

Input Schema

NameRequiredDescriptionDefault
cityNoFilter by city
queryNoFree-text search across business names
tradeNoFilter by trade category

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that results include URLs and claim status, and implies a read-only search operation. However, it does not describe the output format (e.g., list vs single object), pagination, or behavior when no matches are found, leaving some behavioral gaps.

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 a single, front-loaded sentence with no wasted words. It covers the main purpose and the return value efficiently, making it easy for an agent to quickly grasp the tool's function.

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 simple 3-parameter search tool with no output schema or annotations, the description covers the essential context: what is searched, the filter dimensions, and what is returned. While it lacks details on pagination or result limits, these are not critical for basic usage and the description is otherwise complete.

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

Parameters4/5

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

The input schema has 100% coverage for all three parameters, so the baseline is 3. The description adds value by explicitly stating that the parameters can be used in any combination, clarifying the relationship between query, city, and trade beyond the individual descriptions in the schema.

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 clearly states a specific action ('Search') and a specific resource ('CAN-TAP Verified directory of 3,000+ real Canadian businesses'), and mentions the return value (listings with URLs and claim status). This distinguishes it from sibling tools like check_backlink_status and claim_listing.

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 clear context for when to use the tool (searching businesses by name, city, trade, or combination) but does not explicitly name alternatives or exclusion criteria. Sibling tools are present but not referenced, so the guidance is clear but not exhaustive.

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