Template for an iMessage agent that shops and pays with Agentcard: Photon (spectrum-ts) as the iMessage pipe, phone-number OAuth sign-in, and a Claude tool-use loop over the Agentcard MCP server.
Critical failures across all dimensions. Tool definitions exist only as inferred names in src/agent/agent.ts with no visible schema registration, parameter documentation, or output specifications. The 'buy' tool has a lengthy description (180+ chars) but lacks input/output schema. Most tools (check_balance, list_cards, create_card, etc.) have only 1-2 sentence descriptions with zero parameter documentation. No input validation, error recovery guidance, or schema constraints visible. This is a template/stub implementation, not a production-ready MCP server.
Approve a request (money-moving / card-mutating tool requiring explicit user confirmation)
Conversational shopping tool: pass the whole ask in natural language. It is conversational and returns a conversation_id — pass that SAME id back on every follow-up (answering its questions, 'add a coke', 'yes check out') so it continues the SAME order. If a get_instructions tool is available and you are unsure how to shop, call it first.
Check account balance
Close a card (money-moving / card-mutating tool requiring explicit user confirmation)
Create a new virtual card (money-moving / card-mutating tool requiring explicit user confirmation)
Fund wallet (money-moving / card-mutating tool requiring explicit user confirmation)
No input schemas visible for any tool. Cannot verify parameter types, constraints, or descriptions. All 15 tools lack JSON Schema definitions required for LLM tool selection and validation.
14 of 15 tools have descriptions under 50 characters (e.g., 'Check account balance', 'List user's cards'). No context on when to use each tool or what it returns.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 31 | 2025-06-18+ | v2 |
Get instructions on how to use available tools
List user's cards
Manage subscription (money-moving / card-mutating tool requiring explicit user confirmation)
Pay at checkout (money-moving / card-mutating tool requiring explicit user confirmation)
Remove payment method (money-moving / card-mutating tool requiring explicit user confirmation)
Set default payment method (money-moving / card-mutating tool requiring explicit user confirmation)
Setup payment method (money-moving / card-mutating tool requiring explicit user confirmation)
Upgrade plan (money-moving / card-mutating tool requiring explicit user confirmation)
Get current user information
No parameter documentation visible. Tools like 'buy' mention 'conversation_id' in description but no schema shows parameter types, required/optional status, or constraints. LLM cannot infer valid inputs.
No output schemas documented. LLM cannot plan downstream tool calls or extract required fields (e.g., card_id from create_card, balance from check_balance). Breaks tool composition.
Money-moving tools (create_card, fund_wallet, pay_checkout, etc.) marked IRREVERSIBLE/DESTRUCTIVE lack confirmation or dry-run patterns. No error recovery guidance. Agents cannot safely execute these without explicit user approval flow.