Skip to main content
Glama
Sign In

PagSeguro

by io.github.mcp-dir
OverviewDiscussionsAdmin

pagseguro_checkouts_get

Checkouts (links/sessões de pagamento) no PagSeguro. Ações:

  • create: cria um checkout (passe o objeto 'checkout').

  • get: detalhe de UM checkout (requer checkout_id).

  • deactivate: inativa um checkout (checkout_id).

[Flattened action: get]

Bulk support: accepts checkout_ids for batched execution.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pagseguro_checkouts_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
checkoutNo
checkout_idNo
checkout_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

The description claims a "get" action but annotations set readOnlyHint=false, creating a contradiction. Beyond this, the description does not disclose any behavioral traits such as authentication needs, rate limits, or side effects. With annotations already present, the description adds no extra behavioral context.

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 general overview of checkouts and a list of three actions, even though this tool is specifically for 'get'. The unnecessary text and lack of focus on the actual tool's purpose make it inefficient.

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 absence of an output schema and low schema coverage, the description should explain what the tool returns (e.g., fields of a checkout) and how to correctly supply parameters. It fails to provide this information, leaving the agent underinformed.

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 description coverage is 0%, so the description must explain parameters but only mentions checkout_id and checkout_ids briefly. It does not clarify the 'account' parameter or the 'checkout' object (which may be irrelevant for this get action). The bulk support hint is minimal.

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

Purpose3/5

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

The description indicates this tool retrieves details of a checkout ("detalhe de UM checkout") and mentions bulk support with checkout_ids, but it is muddled by including extraneous actions (create, deactivate) that belong to other tools. This ambiguity about single vs. batch and the unnecessary actions reduce clarity.

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 guidance is provided on when to use this tool versus sibling tools like pagseguro_checkouts_create or pagseguro_orders_get. There is no mention of prerequisites, exclusions, or scenarios that favor this tool.

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

All PagSeguro toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources