Skip to main content
Glama
Sign In

Vinhozinho

by br.com.vinhozinho
OverviewDiscussionsAdmin

Ficha de um vinho

ficha_do_vinho
Read-onlyIdempotent

A ficha de um rótulo pelo id que a busca devolveu: tipo, uvas, país e região, corpo, acidez, álcool, harmonização, nota e faixa de preço, o texto da casa (rótulos da casa), os guias pra entender o vinho e as páginas da uva, da região e da vinícola. Wine sheet by id.

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": {
      "id": "<id>"
    },
    "name": "ficha_do_vinho"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesO id do rótulo (só dígitos, texto ou número), como a busca devolve.
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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds substantive context by disclosing that the response is a composite sheet with house notes, guides, and grape/region/winery page references, which is valuable absent an output schema. It stops short of describing not-found or error behavior.

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?

Front-loads the purpose and return contents in one sentence, followed by a short English gloss. The long field enumeration is justified by the lack of an output schema, though it could be more structured.

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?

For a two-parameter read tool without an output schema, the description supplies a useful inventory of returned fields and cross-linked pages. It is less complete on routing versus sibling tools and on invalid-id behavior.

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%, with the id format and lingua enum/default fully documented. The description only reinforces that the id comes from search; it adds no new syntax, constraints, or parameter meaning beyond the schema. Baseline 3 applies.

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 retrieval action: fetch a wine sheet by id, and enumerates the returned content. It does not clearly differentiate this tool from siblings such as pagina_de_uva_ou_regiao or vinicola, especially since it says the sheet includes grape/region/winery pages.

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?

The phrase 'pelo id que a busca devolveu' implies it should be used after a search returns an id. However, no sibling alternative is named and there is no explicit when-not-to-use guidance.

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

All Vinhozinho toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources