Skip to main content
Glama
Sign In
@asyntai/mcp

@asyntai/mcp

Official
by asyntai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Delete a product card

delete_product
DestructiveIdempotent

Delete a product to stop the chatbot from offering it.

Instructions

Remove one product so the chatbot stops offering it.

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

Input Schema

NameRequiredDescriptionDefault
product_idYesProduct id from list_products.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already indicate destructive and idempotent behavior, so the description does not need to restate those. It adds the behavioral outcome that after deletion the chatbot stops offering the product. It does not mention irreversibility, but destructiveHint covers that concern.

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?

The description is a single clear sentence with no filler or redundant information. It efficiently states the action, the object, and the purpose.

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, the description combined with the schema and annotations is sufficient. It explains the effect on the chatbot's offerings, and no output schema exists, so return-value details are not needed. Additional error-case behavior would be nice but is not essential.

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 schema fully documents the only parameter, product_id, including its source from list_products. The description adds no additional parameter-level details, which is acceptable because schema coverage is 100%.

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 states a specific action ('Remove one product') and the intended effect ('so the chatbot stops offering it'). It clearly identifies the resource type and contrasts with sibling tools like delete_image or delete_webhook by being product-specific.

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 purpose clause implies when to use the tool: when a product should no longer be offered. It does not explicitly name alternative tools such as add_product or list_products, but the product_id parameter description references list_products, giving practical guidance for obtaining the required ID.

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

Deploy Server

Other Tools