Skip to main content
Glama

Link a Komers store

link_komers_store

Link the owner's Komers store to this site (its products and Komers checkout). Uses the Komers connection: if the owner hasn't connected Komers yet it returns the connect link (sign in and Allow, like in Claude); once connected it lists their stores to choose from with set_site_komers_store. partner: true starts the older partner store link instead (developers; also what the AI chat bubble and WhatsApp alerts need today).

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite slug (e.g. "kopitiam-muar") or id
partnerNoDevelopers only: use the partner store link instead of the Komers connection

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the safety profile is already given. The description adds real behavior beyond that: this call depends on an external connection, can return a sign-in/Allow link instead of performing the link, and triggers an out-of-band OAuth-style consent. It doesn't state whether a successful link is reversible or what the exact response shape is, but the key state transitions are disclosed.

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?

Front-loaded with the core action and dense with useful detail; there is essentially no filler. The nested parentheticals (auth instructions, partner caveats) make it a single run-on block that takes a second pass to fully parse, which keeps it below a 5.

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?

There is no output schema, so the description must convey return behavior — and it does, explaining the connect-link response versus the store-list response. For a two-parameter, mutation-flagged, open-world tool, the only remaining gap is ambiguity about whether a call ever completes the link itself rather than handing off to set_site_komers_store.

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%, so the schema already documents both parameters and 3 is the baseline. The description still earns credit for adding meaning to `partner`: not just "developers only" but that it selects the older partner store link and is required for AI chat bubble and WhatsApp alerts today — context absent from 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?

States a specific verb and resource ("Link the owner's Komers store to this site") plus the scope of what gets connected (products and Komers checkout). It is clearly distinguishable from siblings like connect_komers, set_site_komers_store, and unlink_komers_store, which are either named or implied by the flow described.

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 a clear branching context: if Komers isn't connected yet it returns the connect link, and once connected it lists stores to pick from with set_site_komers_store — effectively routing the agent to the follow-up tool. It also carves out the partner: true path for developers. It stops short of explicitly stating when to prefer connect_komers over this, but the flow makes the choice inferable.

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