Skip to main content
Glama

iHelpU Seminovos — iPhones usados no RS

Detalhes de um aparelho

detalhes_aparelho
Read-onlyIdempotent

Ficha de um aparelho do marketplace iHelpU pelo id (o id está no fim da URL /loja/produto/).

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": "detalhes_aparelho"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUUID do aparelho.

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, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds the provenance of the id from the store URL, but says nothing about the returned data ('ficha' is only hinted at) or error behavior for invalid ids, which matters since there is no output schema.

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 with the resource and verb first, followed by the practical id hint. No wasted text, though the phrasing is slightly dense.

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 simple single-parameter read tool with full annotation coverage this is close to sufficient, but with no output schema the description could say what a 'ficha' contains (fields returned) to let the agent know what to expect.

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

Parameters4/5

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

Schema coverage is 100% and the schema already defines id as a UUID. The description adds genuine value by telling the agent where the id is found (end of the /loja/produto/<id> URL), which the schema does not.

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 action and resource: fetch the 'ficha' (record/sheet) of an iHelpU marketplace device by id. This distinguishes it clearly from siblings like buscar_iphones (search) and preco_iphone_usado (price lookup), though it does not explicitly name those siblings.

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 parenthetical explaining that the id comes from the end of the /loja/produto/<id> URL gives useful context on when/how to obtain the input. However, it never states when to use this instead of buscar_iphones or preco_iphone_usado, so routing 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