Skip to main content
Glama

Compara MEI: card machines, websites, e-commerce, CRM and ERP for Brazilian small businesses

Ficha completa de um produto

ficha_produto
Read-onlyIdempotent

Todos os dados de um produto: planos e preços em reais com data e fonte, taxas ou recursos, pontos fortes e fracos e link 'comprar'.

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_produto"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid ou nome, ex.: pagbank, infinitepay, nuvemshop, hostinger, bling

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context beyond them: the payload includes price provenance (date and source) and qualitative fields (strengths/weaknesses, buy link), which matters because no output schema exists.

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

Conciseness5/5

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

One dense sentence with no filler, and the most important fact (this returns all data for a product) is front-loaded ahead of the field enumeration. Nothing could be removed without losing information.

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 single-parameter read tool with no output schema, the description adequately compensates by listing the returned content. The remaining gap is failure semantics — what is returned for an unknown or ambiguous product reference — which matters slightly more given openWorldHint=false implies a fixed catalog.

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 100% and the single parameter already documents that it accepts an id or a name, with concrete examples. The description adds nothing further about matching behavior (exact vs partial name) or casing, so the 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?

The description names the resource ('um produto') and enumerates exactly what comes back: plans, prices in BRL with date and source, fees/features, pros and cons, and a purchase link. That content list naturally separates it from a search tool like buscar_produtos or a comparison tool like comparar_produtos, though it never names an alternative explicitly.

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: an agent can infer this is the tool to call once it already has a single product reference and wants full detail. There is no statement of when to prefer it over buscar_produtos or comparar_produtos, and no note on what to do when the product is not found.

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