Skip to main content
Glama

kya_reportBadgeOutcome

Report the merchant's response to a user's badge, specifying whether access was granted, denied, or unparseable.

Instructions

[DEPRECATED — outcomes are now tracked automatically via the verify endpoint. This tool will be removed in a future version.]

Report how the merchant responded when you presented your Badge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
verification_tokenYesThe verification_token returned by kya_getAgentIdentity
merchantYesThe merchant where you presented (e.g., 'starbucks.com')
outcomeYesnot_denied = merchant did not block you; denied = blocked/bot-walled; unparseable = unknown or timed out
trip_idNoTrip ID from kya_getAgentIdentity — links events in this shopping session

Implementation Reference

  • Handler function for the kya_reportBadgeOutcome tool. It is a deprecated MCP tool that acknowledges the outcome (not_denied/denied/unparseable) at a merchant. It merely prints a deprecation warning once on first call and returns an acknowledgment message. No actual API call is made — outcomes are now auto-tracked.
    server.tool(
      "kya_reportBadgeOutcome",
      `[DEPRECATED — outcomes are now tracked automatically via the verify endpoint. This tool will be removed in a future version.]
    
    Report how the merchant responded when you presented your Badge.`,
      {
        verification_token: z.string().describe(
          "The verification_token returned by kya_getAgentIdentity"
        ),
        merchant: z.string().max(200).describe(
          "The merchant where you presented (e.g., 'starbucks.com')"
        ),
        outcome: z
          .enum(["not_denied", "denied", "unparseable"])
          .describe(
            "not_denied = merchant did not block you; denied = blocked/bot-walled; unparseable = unknown or timed out"
          ),
        trip_id: z.string().uuid().optional().describe(
          "Trip ID from kya_getAgentIdentity — links events in this shopping session"
        ),
      },
      async ({ merchant, outcome }) => {
        if (!_warnedOutcome) {
          process.stderr.write("[badge] WARNING: kya_reportBadgeOutcome is deprecated. Outcomes are now tracked automatically.\n");
          _warnedOutcome = true;
        }
        return {
          content: [{
            type: "text",
            text: `Outcome acknowledged: ${outcome} at ${merchant} (deprecated — auto-tracking active).`,
          }],
        };
      }
    );
  • Zod schema defining the input parameters for kya_reportBadgeOutcome: verification_token (required string), merchant (required string, max 200 chars), outcome (required enum: not_denied/denied/unparseable), and trip_id (optional UUID string).
    {
      verification_token: z.string().describe(
        "The verification_token returned by kya_getAgentIdentity"
      ),
      merchant: z.string().max(200).describe(
        "The merchant where you presented (e.g., 'starbucks.com')"
      ),
      outcome: z
        .enum(["not_denied", "denied", "unparseable"])
        .describe(
          "not_denied = merchant did not block you; denied = blocked/bot-walled; unparseable = unknown or timed out"
        ),
      trip_id: z.string().uuid().optional().describe(
        "Trip ID from kya_getAgentIdentity — links events in this shopping session"
      ),
  • src/index.ts:113-146 (registration)
    Registration of the 'kya_reportBadgeOutcome' tool on the MCP server via server.tool(), making it available to MCP clients.
    server.tool(
      "kya_reportBadgeOutcome",
      `[DEPRECATED — outcomes are now tracked automatically via the verify endpoint. This tool will be removed in a future version.]
    
    Report how the merchant responded when you presented your Badge.`,
      {
        verification_token: z.string().describe(
          "The verification_token returned by kya_getAgentIdentity"
        ),
        merchant: z.string().max(200).describe(
          "The merchant where you presented (e.g., 'starbucks.com')"
        ),
        outcome: z
          .enum(["not_denied", "denied", "unparseable"])
          .describe(
            "not_denied = merchant did not block you; denied = blocked/bot-walled; unparseable = unknown or timed out"
          ),
        trip_id: z.string().uuid().optional().describe(
          "Trip ID from kya_getAgentIdentity — links events in this shopping session"
        ),
      },
      async ({ merchant, outcome }) => {
        if (!_warnedOutcome) {
          process.stderr.write("[badge] WARNING: kya_reportBadgeOutcome is deprecated. Outcomes are now tracked automatically.\n");
          _warnedOutcome = true;
        }
        return {
          content: [{
            type: "text",
            text: `Outcome acknowledged: ${outcome} at ${merchant} (deprecated — auto-tracking active).`,
          }],
        };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the purpose and deprecation, but does not explain side effects, permissions, or what happens upon invocation (e.g., whether data is stored, if there are rate limits, or what the response format is).

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?

The description is extremely concise: two sentences with the deprecation warning front-loaded. Every word adds value, and there is no redundant or unnecessary information.

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

Completeness3/5

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

The tool has no output schema and the description does not mention return values or behavioral outcomes. However, the deprecation note and alternative endpoint provide the most critical context (do not use). For a deprecated tool, this is adequate completeness, though for an active tool it would be lacking.

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% with parameter descriptions already provided. The description adds no additional semantic context beyond the schema's own descriptions, so the baseline score of 3 is appropriate.

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 states the tool's purpose: reporting how a merchant responded after presenting a Badge. It also includes a deprecation notice and points to the verify endpoint as the alternative, which distinguishes it from siblings like kya_reportBadgeNotPresented and kya_reportBadgePresented.

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 states that the tool is deprecated and should not be used; outcomes are now tracked automatically via the verify endpoint. This provides clear when-not-to-use guidance and a direct alternative, which is excellent for agent decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kyalabs-Io/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server