Skip to main content
Glama

dia

Read-onlyIdempotent

Retrieve the day's classes, university restaurant menu, calendar events, and nearby activities in one response, with graceful degradation when a source is unavailable.

Instructions

Combina em uma única resposta com degradação graciosa as aulas do dia, o cardápio do Restaurante Universitário, os eventos do Calendário Universitário e as atividades próximas.

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

Input Schema

NameRequiredDescriptionDefault
dataNo
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=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral trait, 'degradação graciosa', meaning partial source failures still return a result, but says nothing about data freshness, caching, or how the composite response signals a failed source.

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 dense sentence that front-loads the aggregation behavior and enumerates the sources without filler. It is efficient, though the enumeration is long enough that the key caveat ('degradação graciosa') is buried mid-sentence.

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?

An output schema exists, so return shape need not be described, and the annotations cover safety. However, for a cross-domain aggregator with three undocumented parameters, the agent still lacks the semantics of 'atualizar' and 'restaurante' and any hint about how missing sources are represented in the response.

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% and the description mentions none of the three parameters. 'do dia' weakly implies the date defaults to today, but the meaning of 'atualizar' (refresh? bypass cache? force re-fetch?) and which restaurant 'restaurante' selects are left entirely unexplained despite a sibling 'restaurantes' existing.

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 names a specific action ('Combina em uma única resposta') plus a concrete set of resources: aulas do dia, cardápio do RU, eventos do Calendário and atividades próximas. An agent can tell this is an aggregate day-overview tool rather than a single-domain tool, though it never explicitly contrasts itself with sibling tools like cardapio, calendario or agenda.

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 only implied: it is the tool to call when you want everything about the day in one shot. There is no explicit statement of when to prefer it over calling the individual domain tools (cardapio, calendario, horario) or of any prerequisite, so the agent must infer the tradeoff.

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