Skip to main content
Glama
Sign In
lightbulb-mcp

lightbulb-mcp

by RPasquale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

stripe_reject

Reject a pending Stripe orchestrator decision by providing the approval ID and an optional reason.

Instructions

Reject a pending Stripe orchestrator decision.

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": {
      "approval_id": "<approval_id>"
    },
    "name": "stripe_reject"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
approval_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The description does not disclose any side effects, authorization requirements, or irreversibility of the rejection. With no annotations provided, the description carries the full burden of behavioral transparency, but fails to add meaningful context beyond the basic action.

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 a single concise sentence with no unnecessary words. It is front-loaded with the action and resource.

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

Completeness2/5

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

Given the tool's simplicity and the presence of an output schema, the description is still too minimal. It fails to explain what rejection means operationally (e.g., effects on other processes, whether it can be undone) and does not help the agent understand the tool's place in the Stripe orchestration workflow.

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?

The input schema coverage is 0%, and the description adds no information about the parameters (approval_id and reason). The agent must infer the meaning of these parameters from the schema alone, which is insufficient.

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 'Reject a pending Stripe orchestrator decision.' clearly states the action (reject) and the resource (pending Stripe orchestrator decision), and effectively distinguishes this tool from its sibling tools such as stripe_approve and stripe_execute_approved.

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?

The description provides no guidance on when to use this tool versus alternatives, such as stripe_approve or when decisions are not pending. There are no explicit context indications or when-not-to-use instructions.

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