Skip to main content
Glama
Sign In

Arrumou Neural

by io.github.brunoreisportela
OverviewDiscussionsAdmin

Registrar pagamento

add_reservation_payment
Destructive

Registra um pagamento (ou estorno) em uma estadia pela forma de pagamento informada. Exige aprovação; não movimenta dinheiro externamente.

Escopo: financials:write · Risco: consequential (prévia + aprovação do usuário obrigatória) · Efeitos: Cria Payment no caixa aberto e registra atividade. · INDISPONÍVEL nesta autorização (escopo não concedido ou papel sem o módulo)

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": {
      "reservation_id": "<reservation_id>",
      "amount": "<amount>",
      "method_id": "<method_id>"
    },
    "name": "add_reservation_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
kindNoPAYMENT
notesNo
amountYes
method_idYes
approval_idNoId de uma aprovação já decidida pelo usuário para esta mesma ação. Omita para receber a prévia e o link de aprovação.
reservation_idYes
idempotency_keyNoChave de idempotência escolhida pelo cliente; repetir a chave com os mesmos dados devolve o mesmo resultado.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond annotations, the description discloses the concrete effect ("Cria Payment no caixa aberto e registra atividade"), clarifies it does not move money externally (consistent with openWorldHint=false), and states the approval requirement. It also discloses a crucial runtime condition (unavailable under this authorization). Rich 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.

Conciseness4/5

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

Front-loads the core action, then uses compact delimited metadata (scope · risk · effects · availability). Dense but efficient; the run-on metadata block is slightly jargony but every clause carries signal.

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?

For a consequential 8-parameter financial mutation with no output schema, the description covers effects and approval but omits the preview→approve→execute workflow and explanations for several parameters. Adequate but with clear gaps given the tool's complexity.

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 only 25%; only approval_id and idempotency_key are documented in the schema. The description adds the payment-method and payment/refund (kind) linkage but leaves date, notes, amount, and reservation_id unexplained, so it does not compensate for the large coverage gap.

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?

States a specific verb+resource+scope: registers a payment (or refund) on a stay via the given payment method. It is clearly distinguishable from siblings like add_reservation_charge and add_reservation_discount because it explicitly scopes to payments/refunds. An agent knows exactly what it does without opening the schema.

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

Usage Guidelines4/5

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

Explicitly flags consequential risk and mandatory approval ("Exige aprovação; ... prévia + aprovação do usuário obrigatória"), and even announces current unavailability ("INDISPONÍVEL nesta autorização"), which is a strong usage signal. However, it does not explicitly route the agent among financial siblings (charge vs discount vs payment), so no full when/when-not guidance.

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

All Arrumou Neural 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