Skip to main content
Glama
MCP Dokploy Online
by igoruam

stripe-updateInvoiceNotifications

Idempotent

Enable or disable Stripe invoice notifications by updating the notification setting with a boolean flag.

Instructions

POST /stripe.updateInvoiceNotifications

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": {
      "enabled": "<enabled>"
    },
    "name": "stripe-updateInvoiceNotifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations only supply openWorldHint and idempotentHint; they say nothing about whether this is a mutation, what permissions are required, or what side effects occur when notifications are enabled. The description adds no behavioral context at all beyond the endpoint path, leaving the mutation semantics entirely undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but shortness here reflects under-specification rather than efficiency. The one line present is a redundant restatement of the tool name and carries no actionable information.

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

Completeness1/5

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

Even for a one-boolean-parameter tool, the definition omits the meaning of the flag, the effect on the account, and the return behavior (no output schema exists). Nothing an agent needs in order to invoke this correctly is present.

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

Parameters1/5

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

Schema description coverage is 0% for the single required 'enabled' boolean, and the description provides no compensating information. It does not state what enabling or disabling actually changes, so the sole parameter's meaning is documented nowhere.

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

Purpose2/5

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

The description is just the HTTP route 'POST /stripe.updateInvoiceNotifications', which restates the tool name rather than explaining what the operation does. It never says what an 'invoice notification' setting is, whether it enables emails, webhooks, or in-app alerts, so an agent cannot distinguish it from siblings such as stripe-getInvoices.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of any alternative tool. An agent would have to guess whether this belongs in a billing-status flow or an invoice-retrieval flow, and there is no exclusion or trigger condition provided.

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

Deploy Server

Other Tools