Skip to main content
Glama

Cheapshark

by io.github.pipeworx-io
OverviewAdmin

Deal

deal
Read-onlyIdempotent

Single deal detail.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dealsNo
gameInfoNo
cheapestPriceEverNo

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "1"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "cheapestPriceEver": {
+      "properties": {
+        "date": {
+          "description": "Unix timestamp of cheapest price",
+          "type": "number"
+        },
+        "price": {
+          "description": "Cheapest price ever recorded",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "deals": {
+      "items": {
+        "properties": {
+          "dealID": {
+            "description": "Deal identifier",
+            "type": "string"
+          },
+          "dealRating": {
+            "description": "Deal rating",
+            "type": "string"
+          },
+          "isOnSale": {
+            "description": "Whether on sale",
+            "type": "boolean"
+          },
+          "lastChange": {
+            "description": "Unix timestamp of last change",
+            "type": "number"
+          },
+          "normalPrice": {
+            "description": "Normal price",
+            "type": "string"
+          },
+          "price": {
+            "description": "Current deal price",
+            "type": "string"
+          },
+          "savings": {
+            "description": "Savings percentage",
+            "type": "string"
+          },
+          "storeID": {
+            "description": "Store identifier",
+            "type": "string"
+          },
+          "storeIcon": {
+            "description": "Store icon URL",
+            "type": "string"
+          },
+          "url": {
+            "description": "Deal URL",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "gameInfo": {
+      "properties": {
+        "gameID": {
+          "description": "Game identifier",
+          "type": "string"
+        },
+        "steamAppID": {
+          "description": "Steam app ID if available",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "thumb": {
+          "description": "Game thumbnail URL",
+          "type": "string"
+        },
+        "title": {
+          "description": "Game title",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

C2.5/5.0
Behavior1/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, fully describing the tool's safety and idempotency. The description adds no additional behavioral context, failing to provide value beyond the structured fields.

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?

At four words, the description is very concise but at the expense of informative content. It is front-loaded but too brief to fully convey purpose and usage. It earns its place, but could be expanded without losing conciseness.

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 simple retrieval tool with one parameter and annotations present, the description is minimally adequate. The existence of an output schema covers return values, but the description lacks details on scope or behavior, leaving gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description should compensate. It implies the 'id' parameter identifies which deal but gives no details on format, constraints, or examples. The single-line description adds minimal meaning beyond the schema.

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 'Single deal detail' clearly identifies the tool's purpose: fetching details for one deal. It distinguishes from sibling tool 'deals' by specifying singular focus, but lacks specifics on what 'detail' includes.

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 usage guidance is provided. The description does not state when to use this tool versus alternatives like 'deals' (list) or other entity tools, nor does it mention prerequisites or exclusions.

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

All Cheapshark toolsInspect
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.

Resources