Skip to main content
Glama

Uva ou região

pagina_de_uva_ou_regiao
Read-onlyIdempotent

O resumo da página de uma uva (27, como Malbec, Touriga Nacional) ou de uma região (30, como Douro, Mendoza, Serra Gaúcha): a abertura, os fatos com a fonte de cada um e o link. Grape or wine region page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "nome": "<nome>"
    },
    "name": "pagina_de_uva_ou_regiao"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomeYesO nome ou o endereço curto ("malbec", "douro", "vale-do-maipo").
tipoNouva ou regiao (opcional: sem ele, a casa procura nas duas).
linguaNoLíngua da resposta e dos links (padrão: a do endereço; /mcp = pt-BR). Response language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 usefully discloses the return payload shape (abertura, facts each with a source, link), but says nothing about behavior when the name matches nothing or matches both a grape and a region.

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

Conciseness3/5

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

It is a single sentence, but the stray '(27' and '(30' figures sit inline with no explanation and interrupt the reading of an otherwise front-loaded summary. The trailing English gloss 'Grape or wine region page.' is largely redundant with the Portuguese text and the title.

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?

With no output schema, the description does carry the burden of describing returns, and it does so adequately at a high level (opening, sourced facts, link). For a lookup tool with an optional type filter and a language parameter, it is missing the not-found and ambiguous-match behavior an agent would need to interpret outcomes.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains 'nome', 'tipo', and 'lingua' fully, making 3 the baseline. The description adds no parameter meaning beyond the schema and in fact introduces unexplained numeric tokens '(27, ...)' and '(30, ...)' that are never defined and risk being misread as page IDs or required arguments.

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 states a specific resource (a grape-variety or wine-region page) and what it returns: opening text, sourced facts, and a link, with examples such as Malbec and Douro. It does not differentiate from siblings like verbete, ficha_do_vinho, or vinicola, which an agent could plausibly confuse with a page-summary lookup.

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 by the grape/region framing; there is no explicit statement of when to prefer this over verbete or ficha_do_vinho, nor any when-not-to-use condition. The 'tipo' optionality behavior is delegated entirely to the schema rather than restated as guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources