Skip to main content
Glama

cardapio_semana

Read-onlyIdempotent

Fetches weekday menus (Monday–Friday) for the University Restaurant from a given week, letting you view all five days at once.

Instructions

Retorna os cardápios dos 5 dias úteis (segunda a sexta-feira) do Restaurante Universitário a partir da semana informada.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cardapio_semana"
  }
}

Input Schema

NameRequiredDescriptionDefault
inicioNo
atualizarNo
restauranteNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description usefully discloses that the result always spans the five business days starting from the given week, but it says nothing about the 'atualizar' refresh/caching behavior or whether results are cached, which is the one genuinely non-obvious trait of this tool.

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

Conciseness4/5

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

A single front-loaded sentence with no redundant wording; the scope constraint (5 business days from the informed week) is stated up front. Nothing needs trimming, though nothing is layered for scanability either.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, but for a 3-parameter tool with zero schema descriptions the definition leaves key ambiguities: the accepted format of 'inicio', what 'a partir da semana informada' means (one week or many), and what 'atualizar' changes.

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?

Schema description coverage is 0%, so the description must carry parameter meaning, and it mostly does not. It indirectly covers 'inicio' ('a partir da semana informada') and hints at 'restaurante' (University Restaurant), but gives no date format for 'inicio' (typed only as string|null) and never explains 'atualizar', which is the least self-explanatory parameter.

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?

States a specific verb ('Retorna') and resource ('cardápios dos 5 dias úteis ... do Restaurante Universitário'), plus the scope (Mon–Fri, from a given week). An agent can tell what it returns, but the description never contrasts it with the sibling 'cardapio' (single day) or 'restaurantes', so sibling differentiation is left to inference.

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?

There is no explicit when-to-use or when-not guidance and no named alternative. The agent must guess whether to call this, 'cardapio', or 'dia' for day-level lookups; only the word 'semana' in the name hints at the intended granularity.

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