Skip to main content
Glama

Lovie Company Formation

Start KYC Inquiry

kyc_start_kyc_inquiry

StartKycInquiry creates a provider inquiry and returns the hosted flow URL. Idempotent within an open inquiry window. Exposed because the Mac app reaches the server only over MCP, and only an inquiry this service opened is one the webhook and GetKycStatus can read.

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": {
      "userId": "<userId>"
    },
    "name": "kyc_start_kyc_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesUUID value wrapper.
templateIdNo
redirectUriNo
trustedDeviceIdNoUUID value wrapper.
trustedDeviceNonceNo
trustedDeviceSignatureB64No

Output Schema

NameRequiredDescriptionDefault
inquiryIdYes
hostedFlowUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / trustedDeviceNonce
      Added value: +{
      +  "maxLength": 255,
      +  "pattern": "^[A-Za-z0-9+/=_-]*$",
      +  "type": "string"
      +}
    • addedInput schema / properties / trustedDeviceSignatureB64
      Added value: +{
      +  "maxLength": 4096,
      +  "pattern": "^[A-Za-z0-9+/=]*$",
      +  "type": "string"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing an external provider interaction, an idempotency window, and downstream coupling with the webhook and GetKycStatus. Still silent on permissions, failure modes, and what is returned when an inquiry is already open.

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?

Front-loaded with verb, side effect, and return value in the first sentence. The third sentence drifts into internal justification ('the Mac app reaches the server only over MCP') that is more rationale than guidance, though it is short enough not to hurt.

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

Completeness3/5

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

Return values are covered by the output schema, so that omission is fine. However, for a six-parameter tool with nested UUID wrappers and trusted-device authentication fields, the description leaves the agent without enough to fill in the schema correctly.

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

Parameters2/5

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

Schema coverage is only 33% and six parameters exist, yet the description says nothing about userId, templateId, redirectUri, or the opaque trusted-device nonce/signature fields. Those trusted-device parameters in particular need description-level explanation that neither schema nor description provides.

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 ('creates a provider inquiry') and names the concrete artifact returned ('hosted flow URL'). It also distinguishes itself from the sibling kyc_get_kyc_status by noting that only inquiries opened here are readable by that tool.

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?

Implies strongly that this is the mandatory entry point for KYC because GetKycStatus/webhooks can only see inquiries opened by this service. It lacks explicit when-not guidance (e.g., what to do if an inquiry is already open elsewhere) and does not point at an alternative for re-reading status.

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.