agentcard

submit_kyc_fields

Submit identity fields for verification: the ones the ID photo didn't carry (listed by missingFields — the tax/ID number always has to be asked since IDs don't print it; call it "SSN" only for US documents and "national ID number" otherwise), corrections to extracted values the user flagged, and the User Agreements acceptance (agreements_accepted, after presenting each agreement verbatim). That number is forwarded directly to the verification provider and never stored by Agentcard. NEVER ask about occupation, income, spending volume, or account purpose — those are filled automatically and must not be asked.

Input Schema

TableJSON Schema

Name	Required	Description
`ssn`	No	US documents: 9-digit SSN, dashes optional. Non-US documents: the national ID / tax number printed on the ID. Forward-only — never stored.
`last_name`	No	Legal last name, exactly as printed on the ID document.
`first_name`	No	Legal first name, exactly as printed on the ID document.
`address_city`	No	City of the residential address.
`phone_number`	No	E.164 with country code, e.g. +14155551234.
`address_line1`	No	Residential street address, line 1 (e.g. 123 Main St).
`address_line2`	No	Residential street address, line 2 — apartment, suite, or unit. Omit if none.
`date_of_birth`	No	YYYY-MM-DD
`address_region`	No	2-letter state code for US (e.g. CA).
`terms_accepted`	No	DEPRECATED — use agreements_accepted. true once the user explicitly accepted the card issuer's cardholder terms.
`address_postal_code`	No	Postal / ZIP code of the residential address.
`agreements_accepted`	No	Keys of the User Agreements the user explicitly accepted, one by one — the FULL required set from the agreements list in the previous step's result. Only pass after presenting each agreement verbatim and getting an explicit yes covering all of them.
`address_country_code`	No	2-letter ISO country code (e.g. US).

Output Schema

TableJSON Schema

Name	Required	Description
`message`	Yes
`nextStep`	No
`missingFields`	No
`verificationUrl`	No	Face-scan link, present once everything is collected.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJul 28, 2026

TDQS

A4.8/5.0

Behavior4/5

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

Discloses that SSN is forwarded to verification provider and never stored by Agentcard, and agreements must be presented verbatim. Annotations show readOnlyHint=false so write behavior is expected; description adds data handling details. Slightly lacking idempotency or side-effect info, but strong overall.

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?

Front-loaded with purpose, then concise details. Every sentence adds value, no redundancy. Efficiently covers all important aspects without extraneous text.

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?

For a 13-parameter tool with output schema, the description covers boundary behaviors (what not to ask), data retention policy, and required user interaction for agreements. Thorough and complete.

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 coverage is 100%, and description adds critical meaning: explains which params correspond to missingFields vs corrections vs agreements, clarifies SSN handling, and mandates agreement presentation. Goes far beyond schema descriptions.

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?

Description clearly states 'Submit identity fields for verification' and lists specific categories (missingFields, corrections, agreements). Distinguishes from sibling tools like submit_kyc_document and start_kyc by specifying its unique role.

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?

Provides explicit when-to-use: when ID photo didn't carry fields, corrections needed, and agreements acceptance. Includes explicit 'NEVER ask' instructions for irrelevant fields. Implicitly distinguishes from siblings like submit_kyc_document (document upload) and start_kyc (initiation).

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

All agentcard tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, especially in areas like card management and shopping. However, the KYC flow has multiple overlapping tools (start_kyc, get_kyc_status, check_kyc_document, submit_kyc_document, submit_kyc_fields) that could confuse an agent despite detailed descriptions.

Naming Consistency4/5

Tool names consistently use snake_case with a verb_noun pattern (e.g., add_funds, create_card, list_cards). A few exceptions like surprise_me and whoami break the pattern but are still intuitive overall.

Tool Count3/5

50 tools is on the high side for a single server, but the broad domain (cards, shopping, KYC, support, settings) partially justifies it. Some tools could be merged (e.g., KYC flow tools) without losing clarity.

Completeness4/5

The tool surface covers core workflows: CRUD for cards, transactions, KYC, support, shopping, and account management. Minor gaps exist (e.g., no update_card general, no cancel order in shopping), but overall the set is comprehensive for the stated purpose.

Resources

Need Help?