Skip to main content
Glama

Business verification (KYC) status

kyc_status
Read-onlyIdempotent

Where this business's verification (KYC) stands and what is left to do: status (NOT_REQUIRED, SANDBOX, SUBMITTED, MORE_INFO, APPROVED, REJECTED), whether calls and messages are held, missing documents, fields to fix, items a reviewer sent back, and the next step, with a link to the portal page where an owner or admin completes it. While verification is pending, calls and WhatsApp sends are refused until it is approved. Documents are uploaded in the portal, not here. Read only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description rightly spends its words elsewhere: it discloses the enforcement consequence (calls and WhatsApp sends refused while pending), the fact that uploads happen in the portal rather than through this tool, and that a portal link is returned. That is real operational context beyond the annotations, with only return-shape details left implicit.

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 definition is a single dense block that front-loads the core answer (status and what is left to do) before the enforcement caveat and the portal/read-only notes. It is longer than most, but nearly every clause carries distinct information; only the trailing 'Read only' mildly duplicates the annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero parameters, no output schema, and simple annotations, the description carries the full descriptive burden and does so thoroughly: it enumerates statuses, lists every returned element (holds, missing documents, fields to fix, reviewer items, next step, portal link), and explains the enforcement effect. An agent can call this confidently without further information.

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 tool takes no parameters, so the baseline is 4 and there is nothing the description could add on parameter meaning. It correctly avoids inventing input semantics.

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 resource and read action: it reports where a business's KYC verification stands and enumerates the status values (NOT_REQUIRED, SANDBOX, SUBMITTED, MORE_INFO, APPROVED, REJECTED). It is easy to distinguish from siblings like call_status or whatsapp_message_status by subject matter, though it never names an alternative to sharpen that contrast.

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?

Usage context is clear: this is the tool to consult when calls or WhatsApp sends are being refused because verification is pending, and it tells you what remains to be done. It also draws a boundary ('Documents are uploaded in the portal, not here'), but gives no explicit when-not guidance or named alternative sibling.

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.