Skip to main content
Glama

Remover item da Vitrine

remove_showcase_item
DestructiveIdempotent

Remove de vez um item da Vitrine pelo id (de list_showcase_items). Não há como desfazer: confirme com o usuário antes. Exige permissão de escrita (bot:write).

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

Input Schema

NameRequiredDescriptionDefault
idYesId do item (list_showcase_items).

Output Schema

NameRequiredDescriptionDefault
successNo
removidoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint and idempotentHint, and the description adds the non-obvious layers: the removal is permanent ('não há como desfazer'), user confirmation is required, and a bot:write permission is needed. That is exactly the auth and irreversibility context annotations cannot express.

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?

Three short sentences: action and key first, then the irreversibility/confirmation warning, then the permission requirement. Nothing is padded and the highest-risk information lands early.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter destructive tool with full annotation coverage and an output schema, the description covers the remaining gaps an agent would care about: permanence, required confirmation, and write scope. No return-value explanation is needed given the output schema.

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 id parameter is already documented with its source. The description repeats the same provenance hint ('pelo id (de list_showcase_items)') without adding format, range, or failure semantics beyond the schema's minimum: 1 constraint.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Remove de vez um item da Vitrine') plus the keying parameter, and names the sibling that yields the id (list_showcase_items). An agent can distinguish this from add_showcase_item, remove_coupon, and the listing tool without opening any schema.

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

Usage Guidelines4/5

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

Gives concrete pre-call conditions: obtain the id from list_showcase_items and confirm with the user first. It does not enumerate alternatives, but among the siblings there is no competing removal path for showcase items, so the missing exclusion is minor.

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