agentcard

submit_user_info

Submit the user's phone number and terms acceptance for a virtual card. Call this after create_card returns user_info_required. Do NOT ask the user for occupation, income, or account purpose — those are never asked. Identity fields (name, date of birth, SSN / national ID, address) belong to the KYC flow: create_card tells you whether it runs conversationally (start_kyc → ID photo → face scan) or via a hosted verification_url. After phone + terms are saved, retry create_card.

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": {
      "phone_number": "<phone_number>",
      "terms_accepted": "<terms_accepted>"
    },
    "name": "submit_user_info"
  }
}

Input Schema

Name	Required	Description	Default
`phone_number`	Yes	User's phone number in international E.164 format with a country code (e.g. +1 555 123 4567, +44 7911 123456)
`terms_accepted`	Yes	Must be true — the user accepted the AgentCard cardholder terms of service

Output Schema

Name	Required	Description	Default
`status`	No	Outcome of the submission: 'saved' when the user information was stored successfully.
`message`	Yes	Human-readable confirmation that the user information was saved.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations indicate this is a mutation (readOnlyHint=false) but not destructive. The description correctly implies a write operation and explains the expected outcome (saves data then retry). No contradictions.

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?

The description is a single coherent paragraph with no redundancy. It efficiently conveys purpose, usage, and exclusions. Could be slightly more structured but is well-organized.

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?

Given the complexity of the sibling tools and the orchestration context, the description thoroughly explains the tool's role in the broader flow, including post-submission actions and limits on user prompts.

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 already provides full coverage with descriptions for both parameters (phone_number format, terms_accepted must be true). The description does not add significant new semantic details beyond the schema, though it contextualizes them within the workflow.

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?

The description clearly identifies the tool's purpose: submitting phone number and terms acceptance for a virtual card. It distinguishes this from other flows like KYC and explicitly ties it to the create_card workflow.

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 guidance: call after create_card returns user_info_required. Also states what not to ask (occupation, income, etc.) and what to do after submitting (retry create_card).

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

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?