Skip to main content
Glama

ShotPulled

by com.shotpulled.mcp
OverviewDiscussionsAdmin

List water recipes

list_waters
Read-onlyIdempotent

List registered waters for the account. The id on each row is the number this account knows that record by, counting from 1 — safe to show, and what other tools expect back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by status: current (unarchived), archived, or all. Defaults to current.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
watersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedOutput schema / properties / waters / items / properties / calcium / type
      Removed value: -"null"
    • removedOutput schema / properties / waters / items / properties / magnesium / type
      Removed value: -"null"
    • removedOutput schema / properties / waters / items / properties / notes / type
      Removed value: -"null"
    • removedOutput schema / properties / waters / items / properties / sodium / type
      Removed value: -"null"
    • removedOutput schema / properties / waters / items / properties / tds / type
      Removed value: -"null"
    • removedOutput schema / properties / waters / items / properties / type / type
      Removed value: -"null"
  2. Changed1 schema field changed
    • addedOutput schema / properties / waters / items
      Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "archived": {
+      "type": "integer"
+    },
+    "calcium": {
+      "type": "null"
+    },
+    "gh": {
+      "type": "integer"
+    },
+    "id": {
+      "type": "integer"
+    },
+    "kh": {
+      "type": "integer"
+    },
+    "magnesium": {
+      "type": "null"
+    },
+    "name": {
+      "type": "string"
+    },
+    "notes": {
+      "type": "null"
+    },
+    "sodium": {
+      "type": "null"
+    },
+    "tds": {
+      "type": "null"
+    },
+    "type": {
+      "type": "null"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "type",
+    "tds",
+    "gh",
+    "kh",
+    "sodium",
+    "calcium",
+    "magnesium",
+    "notes",
+    "archived"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "waters": {
+      "type": "array"
+    }
+  },
+  "required": [
+    "waters"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuinely non-obvious behavior: row ids are account-scoped ordinals counting from 1, safe to expose, and interoperable with other tools — context an agent could not infer from the schema.

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?

Two short sentences, the core operation front-loaded and the id semantics immediately after. Every clause carries information; no filler or repetition of the title.

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?

An output schema exists, so return values need not be described, and the one input parameter is fully specified in the schema. The description covers what matters most for a list tool — the identity semantics of each row — though it omits whether the list is paginated or ordered.

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 description coverage is 100%: the single enum parameter `status` is fully documented (current/archived/all, defaults to current). The description adds nothing about the status filter, so baseline 3 applies.

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?

States a specific verb and resource ('List registered waters for the account'), which is clearly distinguishable from the many list_* siblings by resource type. It does not explicitly contrast with nearest sibling list_recipes/register_water, but the resource noun does the differentiating work.

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 only implied — the note that the id is 'what other tools expect back' hints that this tool is the lookup step before update_water or similar, but no when-to-use / when-not-to-use condition or alternative is stated. Nothing tells the agent why to pick this over directly registering or updating.

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

All ShotPulled toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources