Skip to main content
Glama
Sign In

Moatless

by store.moatless
OverviewDiscussionsAdmin

List my subscriptions

my_subscriptions
Read-only

The actor's subscriptions that are still going, newest first: what they cost, when the current period ends, and whether a release has come out in it (so it'll be charged for).

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": {
      "context": "<context>"
    },
    "name": "my_subscriptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNoThe maximum number of records to return
filterNoA filter to apply to the query: either a condition {"field": ..., "operator": ..., "value": ...} or an {"and": [...]} / {"or": [...]} group of conditions and groups (nestable). Operators: contains, eq, greater_than, greater_than_or_equal, ilike, in, is_distinct_from, is_nil, is_not_distinct_from, less_than, less_than_or_equal, like, not_eq, string_ends_with, string_starts_with. For 'is_nil' the value is true or false; for 'in' the value is an array. Fields: id, stripe_subscription_id, status, paid_through, cancel_at_period_end, period_start, period_end, price_cents, interval, discount_percent, discounted_price_cents, discounted_through, user_id, listing_id, event_payload, discounted?, running?, released_this_period.
offsetNoThe number of records to skip
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. Never include personal data, such as names, email addresses or message text; refer to people by role, such as "the user" or "a buyer".
result_typeNoThe type of result to returnrun_query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. Never include personal data, such as names, email addresses or message text; refer to people by role, such as \"the user\" or \"a buyer\".",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "context"
+]
  2. Changed3 schema fields changed
    • changedInput schema / properties / filter / description
      Previous value: -"A filter to apply to the query: either a condition {\"field\": ..., \"operator\": ..., \"value\": ...} or an {\"and\": [...]} / {\"or\": [...]} group of conditions and groups (nestable). Operators: contains, eq, greater_than, greater_than_or_equal, ilike, in, is_distinct_from, is_nil, is_not_distinct_from, less_than, less_than_or_equal, like, not_eq, string_ends_with, string_starts_with. For 'is_nil' the value is true or false; for 'in' the value is an array. Fields: id, stripe_subscription_id, status, paid_through, cancel_at_period_end, period_start, period_end, price_cents, interval, user_id, listing_id, event_payload, running?, released_this_period."New value: +"A filter to apply to the query: either a condition {\"field\": ..., \"operator\": ..., \"value\": ...} or an {\"and\": [...]} / {\"or\": [...]} group of conditions and groups (nestable). Operators: contains, eq, greater_than, greater_than_or_equal, ilike, in, is_distinct_from, is_nil, is_not_distinct_from, less_than, less_than_or_equal, like, not_eq, string_ends_with, string_starts_with. For 'is_nil' the value is true or false; for 'in' the value is an array. Fields: id, stripe_subscription_id, status, paid_through, cancel_at_period_end, period_start, period_end, price_cents, interval, discount_percent, discounted_price_cents, discounted_through, user_id, listing_id, event_payload, discounted?, running?, released_this_period."
    • changedInput schema / properties / result_type / oneOf
      Previous value: -[
-  {
-    "description": "Run the query returning the matching records (up to `limit`), or return a count of results, or check if any results exist",
-    "enum": [
-      "run_query",
-      "count",
-      "exists"
-    ],
-    "type": "string"
-  },
-  {
-    "properties": {
-      "aggregate": {
-        "description": "The aggregate function to use",
-        "enum": [
-          "max",
-          "min",
-          "sum",
-          "avg",
-          "count"
-        ],
-        "type": "string"
-      },
-      "field": {
-        "description": "The field to aggregate",
-        "enum": [
-          "id",
-          "stripe_subscription_id",
-          "status",
-          "paid_through",
-          "cancel_at_period_end",
-          "period_start",
-          "period_end",
-          "price_cents",
-          "interval",
-          "user_id",
-          "listing_id",
-          "event_payload",
-          "running?",
-          "released_this_period"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "aggregate",
-      "field"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "description": "Run the query returning the matching records (up to `limit`), or return a count of results, or check if any results exist",
+    "enum": [
+      "run_query",
+      "count",
+      "exists"
+    ],
+    "type": "string"
+  },
+  {
+    "properties": {
+      "aggregate": {
+        "description": "The aggregate function to use",
+        "enum": [
+          "max",
+          "min",
+          "sum",
+          "avg",
+          "count"
+        ],
+        "type": "string"
+      },
+      "field": {
+        "description": "The field to aggregate",
+        "enum": [
+          "id",
+          "stripe_subscription_id",
+          "status",
+          "paid_through",
+          "cancel_at_period_end",
+          "period_start",
+          "period_end",
+          "price_cents",
+          "interval",
+          "discount_percent",
+          "discounted_price_cents",
+          "discounted_through",
+          "user_id",
+          "listing_id",
+          "event_payload",
+          "discounted?",
+          "running?",
+          "released_this_period"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "aggregate",
+      "field"
+    ],
+    "type": "object"
+  }
+]
    • changedInput schema / properties / sort / items / properties / field / enum
      Previous value: -[
-  "id",
-  "stripe_subscription_id",
-  "status",
-  "paid_through",
-  "cancel_at_period_end",
-  "period_start",
-  "period_end",
-  "price_cents",
-  "interval",
-  "user_id",
-  "listing_id",
-  "event_payload",
-  "running?",
-  "released_this_period"
-]New value: +[
+  "id",
+  "stripe_subscription_id",
+  "status",
+  "paid_through",
+  "cancel_at_period_end",
+  "period_start",
+  "period_end",
+  "price_cents",
+  "interval",
+  "discount_percent",
+  "discounted_price_cents",
+  "discounted_through",
+  "user_id",
+  "listing_id",
+  "event_payload",
+  "discounted?",
+  "running?",
+  "released_this_period"
+]
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, yet the description still adds real behavior: it filters out ended subscriptions, applies a default newest-first ordering, and explains the derived flag "released_this_period" as meaning the period will actually be charged. It does not mention pagination defaults or whether cancel-at-period-end subscriptions are included.

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

Conciseness4/5

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

A single sentence that front-loads the scope and default ordering, then the returned data. The trailing parenthetical "(so it'll be charged for)" is slightly convoluted but genuinely explains intent rather than padding.

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?

For a six-parameter tool with a nested, nestable filter object and a oneOf result_type, the rich schema carries the mechanical detail while the description covers scope, ordering and semantics of the derived fields. No output schema exists, and the description does cover what comes back, so remaining gaps (pagination, inclusion rules for ending subscriptions) are minor.

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 83% and the parameters (sort, limit, offset, filter, context, result_type) are documented in the schema itself, so the baseline is 3. The description clarifies the meaning of derived output fields like cost and period end but says nothing about how to override the ordering or use filter/result_type, so it adds little parameter-level meaning.

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 actor's subscriptions that are still going, newest first" names the resource, the scope (active/ongoing only) and the default ordering, plus the fields returned (cost, period end, release status). An agent can distinguish this listing of live subscriptions from mutation siblings like cancel_subscription or resume_subscription, though it never names an alternative explicitly.

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 actor's" and "still going" tell the agent this is the current user's active-subscription view, so it should not be used for history or for changing state. There is no explicit when-to-use / when-not-to-use guidance and no pointer to cancel_subscription or resume_subscription for the action-oriented cases.

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

All Moatless toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources