due-diligence

Order an identification package

create_kyc_package

Order a QES-signed identification package for a role-holder of a Lithuanian legal entity. The register says who holds the role; the person proves they are that person by signing a dossier with their own qualified electronic signature, and an attorney-at-law attests the verified correspondence. Returns immediately with an order id and a ceremony URL to give the subject; the outcome arrives later. Poll with get_kyc_package. Billed only when a package is delivered.

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": {
      "code": "<code>",
      "subjectRole": "<subjectRole>",
      "purpose": "<purpose>"
    },
    "name": "create_kyc_package"
  }
}

Input Schema

Name	Required	Description
`code`	Yes	Lithuanian legal-entity code (juridinio asmens kodas).
`purpose`	Yes	Purpose of processing; logged per call. Required for beneficial-owner data.
`subjectRole`	Yes	Which role the subject is claimed to hold in the entity.
`subjectEmail`	No	Optional. When given, Tvarka emails the ceremony link to the subject; otherwise the link is returned for you to deliver.
`idempotencyKey`	No	Reuse for retries of the same create request.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 7, 2026

addedInput schema / properties / idempotencyKey

Added value: +{
+  "description": "Reuse for retries of the same create request.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

AddedAug 14, 2026

TDQS

A4.9/5.0

Behavior5/5

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

No annotations are provided, but the description fully discloses asynchronous behavior (returns immediately, outcome later), billing semantics (only when delivered), and processing transparency (purpose logged per call). Idempotency key is also mentioned for retries.

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?

Description is largely succinct but contains slight redundancy with the phrase 'The register says... signing a dossier...' and the repeated 'Returns immediately... later.' Minor extra context that does not hinder understanding.

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?

Provides a complete picture: creation flow, asynchronous outcome, polling target, delivery options, billing conditions, and a special requirement for beneficial-owner data. No output schema is present, but the description sufficiently explains what is returned.

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

Parameters5/5

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

Schema descriptions cover 100% of parameters. All five parameters are explicitly explained, including the optional subjectEmail behavior and the idempotencyKey purpose. Enums are self-explanatory within context.

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?

Clearly states the action (order), the resource (QES-signed identification package), and the subject (role-holder of a Lithuanian legal entity). Differentiates from sibling get_kyc_package by focusing on creation vs. retrieval.

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

Usage Guidelines5/5

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

Explicitly instructs to poll with get_kyc_package for the outcome, mentions immediate return of order id and ceremony URL, and notes billing only on delivery. Also mentions purpose required for beneficial-owner data.

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

All due-diligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?