Skip to main content
Glama

knowledge-base

by com.tunnelpowered

check_merchant_verification

Check live what a merchant has actually been verified to, and by whom. Call this before acting on a claim that matters — a profile is a cached summary, this is the current answer. Returns level, a signed attestation, an expiry date and the transparency-log position. level "human" means a tunnel employee checked identity, control of the channels, and that the service is real. level "automated" means machines proved the merchant controls the channels its record cites and NOTHING about who they are or whether they deliver — the limitations array says so inside the signed payload. null means neither. Neither level is an endorsement of quality. Treat an answer older than five minutes as stale for anything irreversible. Authentication: none. This tool works with no credentials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe `slug` field from a search_businesses result, or the merchant numeric id.

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description fully discloses that authentication is none, the tool works without credentials, and clarifies that neither level is an endorsement of quality. It describes the return fields and the constraints of each level.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well front-loaded with the main purpose, but the explanation of levels is somewhat lengthy. It could be more concise while retaining all necessary information.

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?

Given no output schema, the description adequately explains what is returned and the semantics. It does not cover edge cases like errors or rate limits, but for a single-param tool it is mostly complete.

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%, and the schema already provides a description for the single parameter 'slug'. The tool description does not add additional meaning beyond what is 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 the tool checks what a merchant has been verified to and by whom, distinguishes it from a cached profile, and explains the meaning of different levels. It is very specific and actionable.

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 advises calling this before acting on a claim that matters, and notes that the profile is a cached summary. It also provides staleness guidance (5 minutes). It does not explicitly mention alternatives but context is clear.

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

All knowledge-base toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but ask_business and ask_business_freeform both serve the core function of asking a question about a listing, which could cause misselection. The detailed descriptions mitigate the overlap, but the similar intent remains a minor ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (ask_, check_, contact_, get_, search_, send_), with only ask_business_freeform adding a modifier that still fits the convention. Naming is predictable and readable.

Tool Count5/5

Nine tools is well-scoped for a knowledge base server, covering discovery (search, get), questioning (ask), asynchronous communication (contact, followup, replies, escalation), and verification. Each tool earns its place without unnecessary bloat.

Completeness5/5

The tool set provides full coverage of the domain: finding businesses, reading profiles, asking structured and freeform questions, escalating unresolved queries, opening and continuing conversations, and checking verification. Poll-based tools handle dead ends explicitly, so there are no obvious gaps.

Resources