Skip to main content
Glama

Unlink the Komers store

unlink_komers_store
Destructive

Disconnect the Komers store from this site (products, checkout, alerts and chat stop).

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": {
      "site": "<site>"
    },
    "name": "unlink_komers_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite slug (e.g. "kopitiam-muar") or id

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 destructiveHint=true and openWorldHint=true, so the reversibility warning is partly pre-supplied. The description does add real value by naming what stops working (products, checkout, alerts, chat), which the annotations cannot convey. It still omits whether store data is retained after unlinking, whether the action is reversible, and what permissions are needed — meaningful gaps for a destructive tool.

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 sentence, front-loaded with the verb and resource, with the consequence parenthesized for immediate context. Nothing is wasted and nothing important is buried.

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 single-required-parameter destructive mutation with no output schema, the definition covers the operation and its user-visible effects. It falls short on the questions an agent most needs before calling a destructive tool: is the unlink reversible, is any data preserved, and how does this differ from the other Komers disconnect tools.

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?

Only one parameter, and its schema description already covers the slug-or-id format at 100% coverage, so the schema does the heavy lifting. The phrase 'from this site' loosely ties the operation to the site parameter but adds no format or resolution detail beyond the schema. 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?

Specific verb+resource: 'Disconnect the Komers store from this site'. It clearly states the operation and even the downstream effects. However, it does not distinguish itself from similarly named siblings such as disconnect_komers, link_komers_store, and set_site_komers_store, so an agent cannot tell from the description alone which of these is the right one.

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 implied by the verb 'Disconnect' — an agent knows this is the teardown counterpart to linking — but there is no explicit when-to-use, no prerequisite (e.g. must the store be linked first?), and no pointer to the alternative disconnect_komers. The condition for choosing this over its near-identical siblings is left to inference.

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