Skip to main content
Glama

Feegow Clinic

by io.github.mcp-dir

feegow_stock_write_movement

Write stock operations in Feegow. Numeric fields MUST be JSON numbers (integers), never strings — Feegow rejects "4" where 4 is expected. Actions:

  • insert: insert new product. PrecoCompra and PrecoVenda are REQUIRED integers (whole numbers, no decimals). Typical fields: NomeProduto (string), TipoProduto, CategoriaID, FabricanteID, ApresentacaoNome (string), ApresentacaoQuantidade, ApresentacaoUnidade, LocalizacaoID, EstoqueMinimo, EstoqueMaximo, DiasAvisoValidade (all integers).

  • entry: product entry into stock. Requires productId (integer), quantity (integer), date (string).

  • movement: product movement between locations.

  • exit: product exit from stock. Requires productId (integer), quantity (integer), date (string).

[Flattened action: movement]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
accountNo

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already indicate destructiveHint=false and readOnlyHint=false. The description adds a useful constraint about numeric fields being JSON numbers, but lacks other behavioral info (e.g., authentication, side effects, reversibility). No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is relatively long but well-structured, starting with a critical warning. However, the final line 'Flattened action: movement' is confusing and adds clutter. Could be more concise without losing essential information.

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 input structure well but omits return values (no output schema) and error handling. For a write operation, agents may need to know success indicators or response format. Adequate but incomplete.

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

Parameters5/5

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

Input schema has 0% description coverage with only two parameters (data and account). The description extensively compensates by detailing the structure within the 'data' JSON string, including required fields for each action (e.g., PrecoCompra, productId). This is critical for correct invocation.

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 states it writes stock operations and lists four specific actions (insert, entry, movement, exit). However, the note 'Flattened action: movement' at the end introduces ambiguity, and the relationship to sibling tools like feegow_stock_write_insert is unclear.

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 provides no guidance on when to use this tool versus the specific sibling tools (feegow_stock_write_entry, feegow_stock_write_exit, etc.). An agent is left to infer usage without explicit context or alternatives.

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
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

D1.9/5.0
Disambiguation1/5

Many tools have identical descriptions (e.g., multiple tools with same 'Read appointments and scheduling data' text) and only differ by a 'flattened action' label, making it impossible for an agent to distinguish which tool to call for a specific operation.

Naming Consistency2/5

Names follow a loose verb_noun pattern but are extremely inconsistent: some use underscores, some have redundant prefixes like 'feegow_appointment_', and the same actions are duplicated across multiple tool names (e.g., 'list' appears in many). The 'flattened action' suffix is confusing.

Tool Count1/5

94 tools is far too many for a clinic management system. This is clearly due to a one-action-per-tool design that fragments the API surface, making the server bloated and hard to navigate. A typical well-structured server for this domain would have 10-20 tools.

Completeness3/5

The server covers many areas (appointments, patients, financial, procedures, stock, etc.), suggesting broad functionality. However, the fragmentation obscures gaps and makes it difficult to determine if all CRUD operations exist for each entity. Some areas (e.g., stock write) have multiple tools for single actions.

Resources