Skip to main content
Glama

Feegow Clinic

by io.github.mcp-dir
OverviewDiscussionsAdmin

feegow_financial_write_create_voucher

Write financial operations in Feegow. Actions:

  • associate_account: associate financial account to patient (account, association).

  • update_nfse: update NFS-e number on invoice (invoice_id, nfse_numero).

  • pay_invoice: pay an invoice.

  • create_invoice: create a new invoice.

  • create_invoice_by_appt: create invoice from appointment.

  • create_voucher: create a voucher.

  • update_voucher: update a voucher.

  • pay_booking: pay a booking (bookingId, amount, associationId, accountId, paymentMethod, paymentDate YYYY-MM-DD).

For destructive removals (remove_invoice, remove_payment, cancel_voucher) use feegow_financial_delete.

[Flattened action: create_voucher]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
accountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/5.0
Behavior2/5

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

Annotations indicate non-read-only and non-destructive, but the description adds no behavioral details like side effects, authorization, or error handling. The note about destructive removals references another tool, not this one.

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 long, listing all possible actions despite being flattened to create_voucher. The key information is buried at the end, not front-loaded.

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?

Incomplete for a write operation: no details on request payload, expected behavior, or response format. Without output schema or parameter descriptions, the agent cannot invoke it correctly.

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?

With 0% schema coverage, the description fails to explain what the 'data' and 'account' parameters represent. It only mentions actions but not the parameter structure or required format for create_voucher.

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

Purpose2/5

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

The description lists multiple actions with a note 'Flattened action: create_voucher', creating ambiguity about the tool's exact purpose. It appears to be a generic write tool but is presented for a single action, confusing the agent.

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 on when to use this tool versus the many sibling write tools (e.g., feegow_financial_write_pay_invoice) or when not to use it. The only alternative mentioned is for destructive removals, which is unrelated.

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

All Feegow Clinic 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