Skip to main content
Glama

WebDiet

by io.github.mcp-dir
OverviewDiscussionsAdmin

webdiet_preconsulta_list_templates

Read-onlyIdempotent

Read pre-consultation questionnaires (Pré-consulta) in WebDiet. Actions:

  • list_templates → list all questionnaire templates the nutritionist publishes. Each item returns nome, descricao, perguntas[] (decoded), modelo, codigo, "link" (the public short URL https://nutr.se/ to share with patients) and "preview_url" (panel preview). USE THIS when the user asks for "o link do questionário de pré-consulta" / "link do formulário".

  • list_responses → list patient submissions to ANY template. Each response has id, id_code, template_nome, origem (anamnese | questionario), respondedor {nome, telefone, nascimento}, data, texto (decoded plain Q/A), texto_html (original HTML), pdf_url. Use filtros tipo (template name) and nome (responder name) to narrow.

  • get_response → fetch one response by id (or id_code/codigo). For LINKING a response to an existing patient (vincular), use webdiet_preconsulta_write action=link_to_patient.

[Flattened action: list_templates]

Bulk support: accepts response_ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nomeNo
tipoNo
limitNo
offsetNo
accountNo
response_idNo
response_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already indicate safe read-only operation. Description adds useful behavioral details: returns specific fields, mentions decoded content, preview URL, and bulk support. No contradictions 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.

Conciseness2/5

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

Description is overly verbose, mixing documentation for multiple tools (list_responses, get_response) into a single tool description. This violates conciseness and structural clarity.

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 listing templates, it provides output field details and usage hints. However, it omits parameter explanations and includes irrelevant information, leaving gaps despite no output schema.

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

Parameters1/5

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

Schema has 7 parameters with 0% description coverage. Description does not explain any parameter except response_ids in bulk context. For 0% coverage, description must compensate but fails to do so.

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 clearly states the tool reads pre-consultation questionnaires and specifically identifies the 'list_templates' action with explicit output fields. However, it includes actions for other tools (list_responses, get_response) which muddles focus.

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

Usage Guidelines3/5

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

Explicitly states when to use this tool (asking for questionnaire link), but does not clearly exclude other use cases or contrast with sibling tools like webdiet_preconsulta_list_responses. The inclusion of other actions may lead to misuse.

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