Komers Sites

Shop settings

set_shop

Shop settings for a site that sells through Komers: which delivery options customers can choose at checkout, a note shown before checkout (e.g. delivery areas or times), product pages on or off, featured product ids, and the published delivery and returns policies (shown on /policies, in llms.txt, the product feed and product schema so AI shopping assistants can quote them). Only the fields you give change. Ask the owner for the real policy; never guess one.

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

Input Schema

Name	Required	Description
`site`	Yes	Site slug (e.g. "kopitiam-muar") or id
`returns`	No	The returns policy to publish; null unpublishes it. For food and drink the honest answer is often accepts: false with a short reason.
`featured`	No
`shipping`	No	The delivery policy to publish; null unpublishes it.
`checkout_note`	No
`product_pages`	No	Server-rendered pages at /p/<id>/<name> for each product (search engines, WhatsApp/Facebook previews, sitemap). Default on.
`delivery_methods`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations mark this as a non-read-only but non-destructive mutation. The description adds important behavior beyond annotations: only supplied fields change, policies propagate to /policies, llms.txt, the product feed, and product schema, and the agent must never guess a policy. Permissions and rate limits are not covered, but the annotations lower the disclosure burden.

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?

The description is front-loaded with the resource scope, then compactly enumerates the settings and two operational rules. The policy-propagation parenthetical is long but earns its place; overall there is little redundancy.

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 7-parameter mutation with no output schema, the description covers the main settings, partial-update behavior, policy propagation, and a safety guardrail. Remaining gaps such as null unpublishing and delivery_methods enum values are handled by the schema, and the lack of explicit sibling routing is a minor omission.

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 57% and the schema itself documents most field semantics. The description names the parameter categories and clarifies featured product ids and policy publication, but adds little syntax or format detail beyond what the schema already provides.

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?

The description states a specific resource ('Shop settings') and enumerates the settings it controls: delivery methods, checkout note, product pages, featured products, and delivery/returns policies. It also scopes the tool to sites selling through Komers, which helps distinguish it from general site settings, though it does not explicitly name a sibling.

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 'for a site that sells through Komers' and the guardrail to ask the owner for the real policy, but there is no explicit guidance on when to use this versus set_site_settings, build_shop, or shop_status.

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

All Komers Sites tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?