Skip to main content
Glama

WebDiet

by io.github.mcp-dir
OverviewDiscussionsAdmin

webdiet_manipulados_write_publish

Create / send / publish / duplicate manipulados in WebDiet. Actions:

  • save → create or update a manipulado for a patient. texto = raw HTML (tinyMCE content), nome = formula name. Omit manipulado_id to create; pass it to update an existing one. Returns id and pdf_url.

  • send → SHORTCUT prescribir + publicar: copia uma ou mais fórmulas do banco (por nome exato vindo de webdiet_manipulados list_banco) para o paciente como manipulados novos. Já fica liberado=true (visível no app/portal do paciente) imediatamente. Skips fórmulas bloqueadas com mensagem de erro.

  • publish → toggle liberar/disponibilizar status (makes the formula visible/invisible on the patient portal/app). Server toggles and returns the NEW state.

  • duplicate → duplicate an existing manipulado (creates a copy "(cópia)").

For destructive delete use webdiet_manipulados_delete.

[Flattened action: publish]

Bulk support: accepts patient_ids, manipulado_ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nomeNo
nomesNo
textoNo
accountNo
patient_idYes
patient_idsNo
manipulado_idNo
manipulado_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Discloses effects beyond annotations: send immediately sets liberado=true, publish toggles and returns new state, save returns id and pdf_url, skip of blocked formulas. The internal note '[Flattened action: publish]' slightly muddies clarity.

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?

Long but structured with action breakdown. Mixed Portuguese/English and internal note increase cognitive load. Could be more concise without losing useful detail.

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?

Covers return values for save and publish, mentions bulk support, cross-refers siblings. Lacks return details for duplicate and bulk execution, and account parameter is unexplained. Adequate but not fully complete for a complex multi-action tool.

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

Parameters3/5

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

Despite 0% schema coverage, description explains most parameters: nome, texto, patient_id, manipulado_id, bulk arrays. Missing account parameter. Partial compensation, not full.

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?

The description clearly states the tool creates/sends/publishes/duplicates manipulados in WebDiet, listing each action with specifics. It distinguishes from sibling webdiet_manipulados_delete for destructive operations.

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

Usage Guidelines5/5

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

Explicitly when to use each action: save for create/update, send as shortcut for prescribir+publicar, publish to toggle visibility, duplicate for copying. Also directs to webdiet_manipulados_delete for deletion.

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

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