Skip to main content
Glama

Pagar.me

by io.github.mcp-dir
OverviewAdmin

pagarme_subscriptions_write_add_usage

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: add_usage]

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

B3.1/5.0
Behavior3/5

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

Annotations provide readOnlyHint and destructiveHint as false; the description adds 'não-destrutivas' (non-destructive) and mentions bulk support. However, it does not disclose side effects, authorization needs, or error behavior, providing limited added value beyond annotations.

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 overly verbose, listing five unrelated actions before narrowing to add_usage. This clutter obscures the tool's primary function and violates conciseness, as each sentence should earn its place.

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 description covers the core operation and bulk support but lacks output schema and fails to clarify the 'data' string format or handle error scenarios. Given the tool's complexity, it is partially complete.

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

Parameters4/5

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

With 0% schema coverage, the description compensates by explaining required parameters for add_usage (subscription_id, item_id) and optional data, as well as bulk fields (subscription_ids, item_ids). It adds meaning beyond the raw schema structure.

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 clearly identifies 'add_usage' as the flattened action and differentiates from sibling tools like pagarme_subscriptions_write_create. However, the broad header 'Criar/operar assinaturas' introduces ambiguity before specifying the actual action.

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 explicit guidance on when to use this tool vs alternatives. The description lists multiple actions but does not direct the agent to avoid using this for creation or other operations, leaving usage context unclear.

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.

Resources