Skip to main content
Glama

Detalhes do produto

get_product
Read-only

Detalhes de um produto pelo código: descrição, medidas da peça, material, preço em reais, disponibilidade, opções obrigatórias (cor, modelo) e variações de tamanho, com o link da página.

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": {
      "codigo": "<codigo>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
codigoYesCódigo do produto (ex.: M10469).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds valuable return-content context, notably that some options (color, model) are mandatory and sizes vary, but it says nothing about behavior when a code is invalid or not found.

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 that leads with the operation and then lists the returned fields. No filler, though the long enumerated list is dense rather than prioritized.

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?

With no output schema, the enumeration of returned fields is exactly what an agent needs to decide whether this tool answers its question, and the mandatory-options/size-variation note prevents surprises. Only error behavior for an unknown code is missing.

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?

Only one parameter, fully documented by the schema at 100% coverage, including an example (M10469) and length constraints. The description adds only 'pelo código', which is already implied by the schema field description, so 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 operation (return product details) keyed by product code, and enumerates exactly what comes back: description, measurements, material, price in BRL, availability, mandatory options (color, model), size variations, and the page link. It is unambiguous, though it does not name a sibling (e.g., search_products) to contrast with.

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: the phrase 'pelo código' signals that this is the lookup to use when you already have a product code. There is no explicit guidance on when to prefer it over search_products or what to do if the code is unknown.

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