Skip to main content
Glama

Kartic

Send Wallet notification

send_wallet_notification
Destructive

Use when a signed-in merchant wants to send a Google Wallet push message to holders of one stamp card. Requires owner or manager. Limited to a few sends per 24 hours. Side effect: sends a real notification to customers.

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": {
      "program_id": "<program_id>",
      "header": "<header>",
      "body": "<body>"
    },
    "name": "send_wallet_notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
headerYes
program_idYesCard program id from list_card_programs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds genuinely non-derivable behavior: the owner/manager authorization requirement, a rate limit of a few sends per 24 hours, and the fact that this reaches real customers. Those are exactly the operational details an agent cannot infer from the schema or annotations.

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?

Four short sentences, front-loaded with the 'Use when' trigger, followed by authorization, rate limit, and side effect in decreasing order of importance. No filler or repetition.

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?

For a three-parameter destructive send with no output schema, the description covers trigger, authorization, throttling, and side effect — the essentials. It is only slightly thin on message-content semantics for header/body, which is the one place an agent could still misfire.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% — program_id is documented in the schema but header and body carry only length constraints. The description mentions 'one stamp card' and 'push message' but never maps these to program_id, header, or body, nor explains what the header and body should contain, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource — sending a Google Wallet push message — and bounds the scope to holders of one stamp card. It doesn't reference any sibling tool, but no sibling in the list plausibly overlaps with a notification-send operation, so confusion risk is low.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use when a signed-in merchant wants to send...' gives a clear triggering context, and 'Requires owner or manager' adds a prerequisite. It stops short of naming when not to use it or pointing to an alternative path for broader audiences, so it stops at clear-context rather than full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources