Cheapshark

Stores

stores

Read-onlyIdempotent

List supported stores.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes	Number of items returned.
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples
```
Added value: +[
+  {}
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "images": {
+            "properties": {
+              "icon": {
+                "description": "Store icon URL",
+                "type": "string"
+              },
+              "logo": {
+                "description": "Store logo URL",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "isActive": {
+            "description": "Whether store is active (1=yes, 0=no)",
+            "type": "number"
+          },
+          "storeID": {
+            "description": "Store identifier",
+            "type": "string"
+          },
+          "storeName": {
+            "description": "Human-readable store name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds no additional behavioral traits, such as whether the list is static or dynamic, or if it requires authentication. It doesn't contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (three words), but it may be too sparse. It could include more context without adding verbosity, such as what 'supported stores' refers to.

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?

With an output schema present, the description partially completes the tool's context. However, it omits details about the nature of stores, potential filtering, or ordering. Adequate for a simple list but not rich.

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?

There are no parameters, so the input schema is fully covered. The description doesn't need to add parameter details; it correctly describes a parameterless call.

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 'List supported stores' uses a clear verb and resource, defining the tool's action. It distinguishes it from sibling tools like 'games' or 'deals', though it doesn't explicitly contrast them.

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. The description doesn't mention any conditions, prerequisites, or context where listing stores is appropriate.

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

All Cheapshark tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.