Skip to main content
Glama

ShotPulled

by com.shotpulled
OverviewDiscussionsAdmin

List grinders

list_grinders
Read-onlyIdempotent

List grinders registered for the account, with status filter. 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, archived, or all. Defaults to current.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
grindersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed33 schema fields changed
    • addedOutput schema / properties / grinders / items / properties / maintenance / properties / calibration / properties / disturbs_note
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / calibration / properties / epoch_at / type
      Previous value: -[
-  "null",
-  "string"
-]New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / calibration / properties / epoch_id / type
      Previous value: -[
-  "null",
-  "integer"
-]New value: +[
+  "integer",
+  "null"
+]
    • addedOutput schema / properties / grinders / items / properties / maintenance / properties / calibration / properties / epoch_task
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / calibration / properties / offset_at / type
      Previous value: -[
-  "null",
-  "string"
-]New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / calibration / properties / offset_source / type
      Previous value: -[
-  "null",
-  "string"
-]New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / calibration / properties / offset_value / type
      Previous value: -[
-  "null",
-  "integer"
-]New value: +[
+  "integer",
+  "null"
+]
    • addedOutput schema / properties / grinders / items / properties / maintenance / properties / calibration / properties / untranslatable_recipe_count
      Added value: +{
+  "type": "integer"
+}
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / calibration / required
      Previous value: -[
-  "stale_recipe_count",
-  "reference_recipe_id",
-  "state",
-  "epoch_id",
-  "epoch_at",
-  "offset_value",
-  "offset_unit",
-  "offset_source",
-  "offset_at",
-  "evidence"
-]New value: +[
+  "stale_recipe_count",
+  "untranslatable_recipe_count",
+  "reference_recipe_id",
+  "state",
+  "epoch_id",
+  "epoch_task",
+  "disturbs_note",
+  "epoch_at",
+  "offset_value",
+  "offset_unit",
+  "offset_source",
+  "offset_at",
+  "evidence"
+]
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / due / properties / burr_clean / properties / basis / type
      Previous value: -[
-  "null",
-  "string"
-]New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / due / properties / burr_clean / properties / done / type
      Previous value: -[
-  "null",
-  "integer"
-]New value: +[
+  "integer",
+  "null"
+]
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / due / properties / burr_clean / properties / every / type
      Previous value: -[
-  "null",
-  "integer"
-]New value: +[
+  "integer",
+  "null"
+]
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / due / properties / burr_clean / properties / ratio / type
      Previous value: -"integer"New value: +[
+  "number",
+  "integer"
+]
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / due / properties / burr_clean / properties / remaining / type
      Previous value: -[
-  "null",
-  "integer"
-]New value: +[
+  "integer",
+  "null"
+]
    • addedOutput schema / properties / grinders / items / properties / maintenance / properties / entries / items / properties / details / additionalProperties
      Added value: +true
    • addedOutput schema / properties / grinders / items / properties / maintenance / properties / entries / items / properties / details / properties
      Added value: +{
+  "from": {
+    "additionalProperties": true,
+    "properties": {
+      "components_spec": {
+        "type": [
+          "null",
+          "string"
+        ]
+      },
+      "nominal_step": {
+        "type": [
+          "number",
+          "integer"
+        ]
+      },
+      "setting_scheme": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "setting_scheme",
+      "nominal_step",
+      "components_spec"
+    ],
+    "type": "object"
+  },
+  "to": {
+    "additionalProperties": true,
+    "properties": {
+      "components_spec": {
+        "type": [
+          "null",
+          "string"
+        ]
+      },
+      "nominal_step": {
+        "type": [
+          "number",
+          "integer"
+        ]
+      },
+      "setting_scheme": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "setting_scheme",
+      "nominal_step",
+      "components_spec"
+    ],
+    "type": "object"
+  }
+}
    • addedOutput schema / properties / grinders / items / properties / maintenance / properties / entries / items / properties / details / required
      Added value: +[]
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / entries / items / properties / details / type
      Previous value: -"null"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / entries / items / properties / evidence / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "null",
+  "string"
+]
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / entries / items / properties / note / type
      Previous value: -[
-  "null",
-  "string"
-]New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / entries / items / properties / offset_at / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "null",
+  "string"
+]
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / entries / items / properties / offset_source / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "null",
+  "string"
+]
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / entries / items / properties / offset_value / type
      Previous value: -[
-  "integer",
-  "null"
-]New value: +[
+  "null",
+  "integer"
+]
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / tasks / items / properties / every / required
      Previous value: -[
-  "days",
-  "shots",
-  "grams"
-]New value: +[]
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / tasks / items / properties / every / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • addedOutput schema / properties / grinders / items / properties / maintenance / properties / tasks / items / properties / opened_by
      Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
    • addedOutput schema / properties / grinders / items / properties / maintenance / properties / tasks / items / properties / scheduled
      Added value: +{
+  "type": "boolean"
+}
    • changedOutput schema / properties / grinders / items / properties / maintenance / properties / tasks / items / required
      Previous value: -[
-  "value",
-  "kind",
-  "label",
-  "sub",
-  "disturbs_zero",
-  "every",
-  "why",
-  "disturbs_note",
-  "offset_unit",
-  "offset_integral",
-  "details_version",
-  "details_fields"
-]New value: +[
+  "value",
+  "kind",
+  "label",
+  "sub",
+  "disturbs_zero",
+  "every",
+  "why",
+  "disturbs_note",
+  "offset_unit",
+  "offset_integral",
+  "scheduled",
+  "opened_by",
+  "details_version",
+  "details_fields"
+]
    • changedOutput schema / properties / grinders / items / properties / max_value / type
      Previous value: -[
-  "integer",
-  "null"
-]New value: +[
+  "null",
+  "integer"
+]
    • changedOutput schema / properties / grinders / items / properties / microns_per_step / type
      Previous value: -[
-  "null",
-  "integer"
-]New value: +[
+  "integer",
+  "null"
+]
    • changedOutput schema / properties / grinders / items / properties / min_value / type
      Previous value: -[
-  "integer",
-  "null"
-]New value: +[
+  "null",
+  "integer"
+]
    • changedOutput schema / properties / grinders / items / properties / nominal_step / type
      Previous value: -"integer"New value: +[
+  "number",
+  "integer"
+]
    • changedOutput schema / properties / grinders / items / properties / notes / type
      Previous value: -"null"New value: +[
+  "string",
+  "null"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds valuable context beyond those annotations by explaining the `id` semantics: account-local numbering starting at 1, safe to display, and expected by other tools. This helps the agent understand how returned values relate to other operations.

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 concise sentences with no filler. The main purpose is front-loaded, and the second sentence provides a key behavioral detail about the returned identifier without over-explaining.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, read-only list tool with a rich output schema and strong annotations, the description is complete. It clarifies account scoping, explains the id contract, and leaves no essential caller-facing gaps.

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?

The input schema provides 100% coverage: the single `status` parameter has a descriptive enum (current, archived, all) and default value. The description only repeats the phrase 'status filter' without adding new parameter-level detail, so it meets but does not exceed the baseline.

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 states a specific verb ('List'), a clear resource ('grinders'), and a scope ('registered for the account'). It also mentions the status filter, making the operation unambiguous and easily distinguishable from sibling list tools for other resources.

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

Usage Guidelines4/5

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

The description clearly conveys when to use the tool: to retrieve grinders for the account, with an optional status filter. It does not explicitly name alternatives or exclusions, but for a simple list operation the context is sufficiently clear.

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