BugSecure MCP

Get my KYC verification status

get_my_kyc_status

Read-onlyIdempotent

Check your BugSecure KYC verification status and see which required documents are on file to confirm if identity verification is complete.

Instructions

Whether the signed-in user’s identity verification (KYC) is complete: overall status and which required documents are on file. Status only — documents themselves are never available here; they are uploaded and managed on the BugSecure website.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No
`isComplete`	No
`hasIdDocument`	No
`hasProofOfAddress`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds meaningful context by clarifying that only status is returned and that documents are never exposed, preventing a likely misconception about the tool's output.

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?

Two tight sentences with no filler. The main purpose is stated first and the important exclusion (documents not available) is front-loaded in the second sentence.

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?

Given there are no parameters, annotations cover the safety profile, and an output schema exists for return values, the description fully covers what an agent needs to call the tool correctly and interpret its scope.

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 has zero parameters and schema coverage is 100%, so there is nothing for the description to add. This matches the baseline for parameterless tools.

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?

States a specific verb and resource: retrieves the signed-in user's KYC verification status. Clearly defines the scope as overall status plus which required documents are on file, and distinguishes itself from document retrieval by explicitly saying documents are never available here.

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?

Indicates the tool is for checking whether identity verification is complete and explicitly states that documents themselves are not available, steering users away from expecting document access. It also mentions documents are managed on the BugSecure website, giving an alternative for document handling, though it doesn't name a sibling tool.

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