Receitas Tradicionais Canônicas
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| onboarding_questionsB | Fornece perguntas sem coletar identidade, diagnosticar ou persistir o perfil. |
| plan_researchC | Após confirmação alimentar e desambiguação, planeja a primeira busca do host. |
| validate_researchC | Verifica declarações documentais, sem acessar páginas ou provar sua veracidade. |
| validate_deliveryB | Confere lote, perfil, inventário e revisão declarada, sem certificar segurança alimentar. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| project_instructions | Instruções embarcadas no pacote, disponíveis sem depender do diretório de documentação. |
TDQS
Scored across 4 tools
Tools have distinct purposes: two validation types (research vs delivery), one planning, and one onboarding. The shared 'research' theme in validate_research and plan_research could cause slight confusion, but descriptions clearly delineate their boundaries.
Most tools follow a consistent snake_case verb_noun pattern (validate_research, validate_delivery, plan_research), but onboarding_questions is a noun phrase, a minor deviation from the convention.
With 4 tools, the set is well within the ideal 3–15 range and each tool appears to serve a specific, non-redundant role in the workflow.
The server name suggests a recipe domain, yet there are no tools to retrieve, create, update, or list recipes. The surface focuses only on validation and planning meta-tasks, leaving significant gaps for core recipe operations.