Skip to main content
Glama

cardapio

Read-onlyIdempotent

Query the UFC university restaurant menu for a specific date, meal, and restaurant, including vegetarian options and gluten or lactose alerts.

Instructions

Consulta o cardápio do Restaurante Universitário (RU) da UFC em uma data específica, incluindo opções vegetarianas e alertas de glúten e lactose.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNo
refeicaoNotodas
atualizarNo
restauranteNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.2/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 the safety profile is covered. The description adds the content shape (vegetarian options, gluten/lactose alerts) but says nothing about the semantics of 'atualizar' (cache refresh) or how results are sourced, which are the real behavioral unknowns here.

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?

One front-loaded sentence that moves from action to scope to payload, with no filler. It is appropriately short for a read-only lookup, though it omits details that would have been worth the extra words.

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?

Return values are covered by the output schema and safety by annotations, so the core is intact. However, for a four-parameter tool with no schema documentation, leaving the meal, restaurant and refresh parameters undefined makes the definition only marginally sufficient.

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 all four parameters, yet it only implies the 'data' parameter. The meal filter enum ('desjejum'/'almoco'/'jantar'), the refresh flag, and the restaurant selector are left entirely unexplained despite 'restaurantes' existing as a sibling.

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+resource ('Consulta o cardápio do Restaurante Universitário') and narrows scope to 'em uma data específica', which implicitly separates it from the weekly-menu sibling. It does not name the sibling explicitly, so it stops short of a 5.

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?

Usage is implied rather than stated: 'em uma data específica' hints that this tool is for single-date lookups versus the weekly menu, but there is no explicit when/when-not guidance and no mention of the alternatives.

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