payclaw-mcp

kya_reportBadgePresented

Report badge presentation to a merchant after merging checkoutPatch, to record the shopping trip for kyaLabs.

Instructions

Report that you presented your Badge to a merchant. Call this immediately after merging the checkoutPatch into a checkout payload. Required for kyaLabs to record the trip.

When Extended Auth is enabled, kyaLabs checks back 7 seconds later. Otherwise, call kya_reportBadgeOutcome when you know the result.

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": {
      "verification_token": "<verification_token>"
    },
    "name": "kya_reportBadgePresented"
  }
}

Input Schema

Name	Required	Description
`verification_token`	Yes	The verification_token returned by kya_getAgentIdentity
`merchant`	No	The merchant name (e.g., 'starbucks.com'). Provide merchantUrl or merchant.
`merchantUrl`	No	The merchant base URL (e.g., 'https://starbucks.com'). Preferred over merchant.
`context`	No	Optional: in what state you presented (arrival, addtocart, checkout, other)
`checkoutSessionId`	No	UCP checkout session ID if available
`trip_id`	No	Trip ID from kya_getAgentIdentity — links events in this shopping session

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.1Mar 18, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so description carries the burden. It discloses the tool triggers a kyaLabs record and mentions a 7-second check when Extended Auth is enabled, but does not clarify idempotency, side effects, or error behavior. Lacks full behavioral disclosure.

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?

Two concise paragraphs: first states purpose and timing, second adds conditional logic. No redundant sentences, front-loaded with key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, timing, and conditional behavior well. However, no output schema exists and description does not mention what the tool returns (e.g., success/error), leaving a gap for agent to understand invocation outcome.

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 baseline is 3. The description adds no parameter-specific guidance beyond what the schema already provides, so no extra value.

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 tool reports presenting a badge to a merchant, specifies timing relative to checkoutPatch merge, and differentiates from sibling kya_reportBadgeOutcome with conditional logic.

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 tells when to call (immediately after merging checkoutPatch) and when not to (Extended Auth enabled: no need for outcome; otherwise call kya_reportBadgeOutcome). Provides clear usage context.

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

Deploy Server