Skip to main content
Glama

restaurantes

Read-onlyIdempotent

List the five UFC university restaurant campus units and their aliases so you can identify the correct location by name, such as Fortaleza or Pici.

Instructions

Lista estática das 5 unidades/campi (Fortaleza, Russas, Quixadá, Crateús, Sobral) do Restaurante Universitário da UFC e seus apelidos; use o nome, ex.: Fortaleza ou Pici.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.6/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 genuine behavioral trait beyond them: the list is "estática", i.e. fixed data that will not change between calls. It says nothing about format or ordering, but with an output schema present that burden is lifted.

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 states what the tool returns and then the usage note. Enumerating all five campus names is somewhat verbose but serves as concrete examples for the agent. No filler or redundant phrasing.

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

Completeness4/5

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

This is a zero-parameter static lookup with an output schema, so almost nothing needs to be in the description beyond identifying the resource. The description covers the resource, the count, the naming scheme and the static nature. Only an explicit pointer to the tools that consume these names is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which is the baseline-4 case. The description still adds value by explaining the naming convention of the entities involved ("use o nome, ex.: Fortaleza ou Pici"), clarifying that names and nicknames both refer to the same units.

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?

"Lista estática das 5 unidades/campi ... do Restaurante Universitário da UFC e seus apelidos" names a specific resource (campus units of the university restaurant) and what is returned (unit names plus nicknames). An agent can distinguish this from menu-related siblings such as cardapio or cardapio_semana because the resource is the unit list, not the meal schedule. It stops short of explicitly naming a sibling to defer to, so it is clear but not maximally differentiated.

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?

"use o nome, ex.: Fortaleza ou Pici" implies the tool exists to resolve valid restaurant identifiers for use in other calls, which is a real usage hint. However, it never states when to call this tool versus a sibling, nor any exclusion or prerequisite. Usage is implied rather than prescribed.

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