Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Full Worldwide KYC FULL

post_risk_WW_kyc_full
Read-onlyIdempotent

Creates a full KYC request to screen individuals or entities for politically exposed persons, adverse media, local politicians, legal enforcement, sanctions, and whitelists.

Instructions

Create a full KYC request on a subject.

Covers politically exposed persons, adverse media, local politicians, legal enforcement, sanctions, and whitelists. Use name for entity types L, W, VE, AC, NA or firstName and lastName for entity type I.

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": {
      "firstName": "<firstName>",
      "lastName": "<lastName>",
      "entityType": "<entityType>",
      "name": "<name>"
    },
    "name": "post_risk_WW_kyc_full"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesthe name of the entity if not Individual
lastNameYeslastName of the person
firstNameYesfirst name of the person
entityTypeYesone of I, L, W, VE, AC, or NA

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true and idempotentHint=true, yet the description tells the agent to 'Create a full KYC request' and the tool name is prefixed 'post_', which reads as a state-changing submission. Beyond that, the description says nothing about cost, latency, whether a request ID is returned, or what the response contains, all of which matter for a screening call with no output schema.

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?

Three short sentences, front-loaded with the purpose followed by coverage and field-routing rules. The hard line breaks are cosmetic noise but no sentence is wasted.

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

Completeness2/5

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

With no output schema and no annotations covering latency or return shape, the description should say what the agent gets back (a request ID? an immediate screening result? an async handle?), and it does not. For a multi-source worldwide KYC check with four required parameters, that is a significant omission.

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?

Schema coverage is 100%, but the description adds real meaning the schema does not: it explains that `name` is the identifier for entity types L, W, VE, AC and NA, while `firstName`/`lastName` are required only for type I. This resolves the ambiguity created by all four fields being marked required in the schema.

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?

States a specific verb and resource ('Create a full KYC request on a subject') and enumerates the screening domains covered (PEP, adverse media, local politicians, legal enforcement, sanctions, whitelists). It does not differentiate itself from nearby WW screening siblings such as get_company_WW_advanced, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance: it never says whether this is for individuals vs companies, whether it is a synchronous result or an async submission (the catalog contains check_async_status, so that distinction matters), or when a lighter sibling should be used instead. The only routing advice is which field to populate for which entity type.

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