Skip to main content
Glama

WebDiet

by io.github.mcp-dir
OverviewDiscussionsAdmin

webdiet_preconsulta_list_responses

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

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

A3.8/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=true and destructiveHint=false, which description aligns with by stating 'Read pre-consultation questionnaires'. Additionally, description discloses bulk support via response_ids, which adds value beyond 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?

Description is somewhat verbose, listing three actions but only list_responses applies. It includes Portuguese phrases and redundant detail. Could be more concise while preserving 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?

Explains the output structure for responses (id, id_code, etc.) but omits parameter descriptions for 5 out of 7 parameters. With no output schema, more detail on pagination and account is needed for complete context.

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?

Only two parameters (nome, tipo) are semantically explained as filters for responder name and template name. With 0% schema coverage and 7 parameters, description fails to explain limit, offset, account, response_id, and response_ids purpose.

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?

Description clearly states it reads and lists patient submissions to pre-consultation questionnaires. It explicitly distinguishes from sibling tools like webdiet_preconsulta_list_templates and webdiet_preconsulta_get_response by describing each action and noting this tool is for list_responses.

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?

Provides guidance on when to use this tool (list responses) vs. alternatives (list_templates for links, get_response for single response, link_to_patient for linking). Mentions filtering by tipo and nome. Lacks explicit 'do not use' scenarios but is still helpful.

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