Skip to main content
Glama

Ver disponibilidade

ver_disponibilidade
Read-only

Disponibilidade ao vivo por tamanho: "pronta" (pronta entrega, fica pronta em até 3 dias) ou "encomenda" (15 dias úteis). Nunca falta: o que não está em estoque sai sob encomenda.

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": {
      "modelo": "<modelo>"
    },
    "name": "ver_disponibilidade"
  }
}

Input Schema

NameRequiredDescriptionDefault
corNoOpcional. Sem cor, devolve todas.
modeloYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context — the lead times of 3 days vs 15 business days and the rule that nothing is ever out of stock because items fall back to made-to-order — but says nothing about the shape or granularity of the returned availability data.

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?

Two compact sentences that front-load the core concept and then explain the two states. There is mild redundancy in 'pronta entrega, fica pronta em até 3 dias', but nothing extraneous overall.

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?

For a read-only lookup with no output schema, the description covers the semantics of the result values but not the structure of the response (which sizes are listed, how per-model/per-colour results are grouped). Given the tool's simplicity and the readOnly annotation, it is adequate but leaves a real gap an agent would want filled.

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 coverage is 50%: cor carries its own description and default behaviour ('Sem cor, devolve todas'), while modelo has none. The description adds no meaning about either parameter and its 'por tamanho' framing does not map onto modelo/cor, so it neither compensates for the gap nor clarifies the enum choices.

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 resource — live availability — and defines the two availability states it returns, which makes it distinguishable from ver_catalogo in principle. However, it says availability is 'por tamanho' while the schema exposes modelo and cor, so an agent cannot immediately tell whether 'tamanho' is a return dimension or a missing parameter — a small ambiguity in an otherwise clear purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the availability values mean but never says when to call this tool versus siblings such as ver_catalogo, ver_pedido, or fechar_compra, nor does it state any prerequisite (e.g., check availability before closing an order). Usage must be inferred.

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