Skip to main content
Glama
Sign In
SimpleShop MCP

SimpleShop MCP

by mikz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

simpleshop_find_products

Find SimpleShop products using search filters or explicit product IDs. Supports text search, product types, pagination, and variant inclusion.

Instructions

Find SimpleShop products by search filters or explicit product IDs.

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": {
      "query": "<query>"
    },
    "name": "simpleshop_find_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesObject query. Use {"mode":"search"} to list/filter products, or {"mode":"by_ids","ids":[...]} for explicit product IDs.

Output Schema

NameRequiredDescriptionDefault
productsYes
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, description should disclose behaviors like pagination, rate limits, or authentication, but only states basic operation. No behavioral details beyond what the name implies.

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?

Single sentence, no wasted words, purpose immediately clear.

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?

Output schema exists, so return values need not be explained. However, the dual-mode operation is only hinted at; schema fills in details, but description could summarize mode behavior more clearly.

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 100%, so the description adds no extra parameter meaning beyond high-level mention of filters and IDs. Baseline 3 is appropriate.

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 the tool finds SimpleShop products using search filters or explicit IDs. It distinguishes from sibling tools like find_documents and get_metadata.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, no when-not-to-use or prerequisites provided.

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