Skip to main content
Glama
Sign In

GoodBarber

by dev.goodbarber
OverviewDiscussionsAdmin

Delete product PDF

shop_delete_product_pdf
Destructive

Deletes the PDF file associated with a given product. Guidance: Deletes the PDF file associated with a given product. | context: product_id

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": {
      "product_id": "<product_id>"
    },
    "name": "shop_delete_product_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesUnique ID of the product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The description matches the destructiveHint annotation and states that the PDF is deleted, but it does not add extra context about irreversibility or side effects beyond what the annotations already convey.

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

Conciseness3/5

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

The description is short but contains redundant phrasing: the first sentence is repeated under 'Guidance' and the trailing '| context: product_id' is awkwardly appended. It is concise but not well structured.

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 simple single-parameter destructive operation with no output schema, the description is sufficient to understand what the tool does. It could mention that only the PDF is removed, not the product, but that is implied by the wording.

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?

The only parameter, product_id, is documented in the schema as 'Unique ID of the product.' The description merely refers to 'a given product' and adds no meaningful semantic detail beyond the schema.

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?

The description clearly states a specific action ('Deletes the PDF file') and a specific resource ('associated with a given product'), distinguishing it from deleting the product itself or uploading a PDF.

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?

The description makes it obvious that this tool is for removing a product's PDF file, while sibling tools like shop_delete_product or shop_upload_product_pdf imply the boundary. It does not explicitly name alternatives, but the intent is clear from the wording.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GoodBarber toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources