Skip to main content
Glama

Pagar.me

by io.github.mcp-dir

pagarme_subscriptions_write_update_payment_method

Criar/operar assinaturas no Pagar.me V5 (só sk_; não-destrutivas). Ações:

  • create: cria assinatura (data: customer_id/customer, plan_id ou items[], payment_method, card_id, …).

  • update_card: altera cartão (requer subscription_id; data).

  • update_payment_method: altera meio de pagamento (requer subscription_id; data).

  • update_billing_date: altera data de cobrança (requer subscription_id; data).

  • add_item: adiciona item (requer subscription_id; data).

  • add_usage: registra uso de item medido (requer subscription_id + item_id; data opcional).

[Flattened action: update_payment_method]

Bulk support: accepts subscription_ids, item_ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
accountNo
item_idNo
item_idsNo
subscription_idNo
subscription_idsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

The description labels the tool as "não-destrutivas" (non-destructive), which aligns with destructiveHint=false in annotations. However, it does not disclose additional behavioral traits such as required permissions, side effects on other resources, or idempotency beyond what annotations already provide.

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?

The description is cluttered with a list of actions for a multi-action tool, even though this tool represents only one action. Important details (requirements, bulk support) are buried. A more focused description for this specific action would be more concise and efficient.

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?

The tool has no output schema and limited parameter documentation. The description specifies required parameters for the action and mentions bulk support, but does not explain the expected return value or the structure of the 'data' field. Given the complexity of payment operations, more completeness is needed.

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?

With 0% schema description coverage, the description helps by stating that for this action, subscription_id and data are required. However, it does not explain what the 'data' string should contain (e.g., payment method fields). The schema lists all params as optional, creating a slight inconsistency with the description's requirement statement.

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 title and description clearly indicate this tool updates the payment method of a Pagar.me subscription ("update_payment_method"). The description lists multiple actions but singles out this one as the flattened action. It distinguishes from sibling tools like pagarme_subscriptions_write_create or pagarme_subscriptions_write_update_card.

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 lacks explicit guidance on when to use this tool versus alternatives. It mentions bulk support but does not state prerequisites, conditions, or when not to use it. No comparisons to siblings are provided.

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

All Pagar.me toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.3/5.0
Disambiguation1/5

The flattened action pattern creates dozens of tools with nearly identical descriptions (e.g., pagarme_charges_get, pagarme_charges_list, pagarme_charges_summary, pagarme_charges_get_many all share the same description except for the action name). An agent cannot easily distinguish which tool performs which specific read operation without parsing the final action line.

Naming Consistency3/5

The Pagar.me API tools follow a consistent pagarme_<entity>_<action> pattern, but the meta-tools (authenticate, connect, marketplace, report_bug, etc.) break the pattern. Additionally, the write/read split is not uniformly applied (some entities separate get/list into tools while others combine them).

Tool Count1/5

86 tools is extremely high for any server. Most of these are redundant: the same operations could be exposed via 5-10 parameterized tools. The flattened action approach inflates the count unnecessarily, creating cognitive overload and search cost for agents.

Completeness3/5

The Pagar.me V5 API coverage is fairly comprehensive across cards, charges, customers, orders, subscriptions, plans, recipients, transfers, and payables. However, the legacy V1-V4 tools duplicate many V5 operations, and there are minor gaps (e.g., no update for cards, no delete for subscriptions). The meta-tools (authenticate, connect, etc.) are unrelated to the payment domain, making the surface feel unfocused.

Resources