Skip to main content
Glama
Sign In
Agentic AQUA

Agentic AQUA

Official
by AquaWallet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

eulen_kyc_confirm

Reconcile a Noviuz Hosted KYC session with Ankara using its opaque session_id to return authoritative status, EUID, final verification, and polling guidance.

Instructions

Ask Ankara to reconcile a Noviuz Hosted KYC session. Pass only the opaque session_id returned by eulen_kyc_session. Ankara obtains the authoritative status and EUID server-to-server. Poll every 15-20 seconds while session_status is 'created'; under_review is NOT verified. Returns is_final, is_success, poll_after_seconds and next_step.

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": {
      "email": "<email>",
      "session_id": "<session_id>"
    },
    "name": "eulen_kyc_confirm"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesJAN3 account email that owns the KYC session
session_idYesOpaque session id returned by eulen_kyc_session

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that status and EUID are obtained server-to-server rather than trusted from the client, defines the polling contract, and clarifies what 'under_review' does and does not mean. It omits auth/permission requirements and whether calling it mutates or is idempotent, which keeps it short of a 5.

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?

Five compact sentences, front-loaded with the action and the input constraint before the polling and return details. No filler; each clause conveys a distinct rule the agent needs.

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?

Two required params, no output schema, no annotations — yet the description covers inputs, the polling loop, state semantics, and the exact return fields (is_final, is_success, poll_after_seconds, next_step). An agent has everything needed to call and interpret it correctly.

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

Parameters3/5

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

Schema coverage is 100%, so both parameters are already documented, and the baseline is 3. The description reinforces that session_id must be the opaque token from eulen_kyc_session (useful), but adds nothing about the required email parameter beyond what the schema says.

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 ('reconcile a Noviuz Hosted KYC session') and names the counterpart system (Ankara) doing the authoritative lookup. It also distinguishes itself from the sibling eulen_kyc_session by stating that the session_id originates there, so an agent can route without opening either schema.

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?

Gives explicit operational guidance: poll every 15-20 seconds while session_status is 'created', and a hard exclusion that under_review is NOT verified. It also constrains input to 'pass only the opaque session_id', which prevents an agent from inventing its own identifiers.

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

Deploy Server

Other Tools