BasketWatch

Your credit balance

check_credits

Read-onlyIdempotent

How many BasketWatch credits the signed-in account has left, and when they expire. Free to call. One credit is one record returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_credits"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`plan`	No
`metered`	No	True when the account pays per record from credits
`expiring`	No	Credits still to expire, soonest first: credits, expires_at (UTC) and bought_at. Credits last 30 days from purchase and the soonest to expire are spent first
`next_expiry`	No	When the next credits expire (UTC), or null
`never_expires`	No	Credits bought before 15 October 2026, which do not expire
`credits_remaining`	No	One credit is one record returned

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 15, 2026

addedOutput schema / properties / expiring

Added value: +{
+  "description": "Credits still to expire, soonest first: credits, expires_at (UTC) and bought_at. Credits last 30 days from purchase and the soonest to expire are spent first",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "title": "Expiring",
+  "type": "array"
+}

addedOutput schema / properties / never_expires

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Credits bought before 15 October 2026, which do not expire",
+  "title": "Never Expires"
+}

addedOutput schema / properties / next_expiry

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "When the next credits expire (UTC), or null",
+  "title": "Next Expiry"
+}

First observedOct 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered by structured data. The description adds information those annotations cannot carry: that the call costs nothing and that one credit equals one record returned, which shapes how an agent reasons about budget.

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?

Three short sentences, no filler, with the primary answer (how many credits remain) placed first. Every clause carries information the agent cannot get from the schema or annotations.

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 zero-parameter read tool with an output schema, this is complete: the description explains what the balance represents, when credits expire, and the cost model for consuming them. Nothing needed to invoke or interpret the call is missing.

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?

The tool takes no parameters, so the baseline is 4 and there is nothing further the description could say. The 'one credit is one record returned' line adds semantic meaning to the returned value rather than to a parameter.

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?

States a specific resource (BasketWatch credits) and the exact information returned: remaining balance and expiry timing. It is clearly distinct from every sibling tool, all of which deal with product pricing rather than account credits.

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?

The description notes the call is free, which is genuinely useful usage context (an agent can check balance without burning credits), but it never states when to call it or in what workflow it belongs. No alternatives or exclusions are needed given there is no overlapping sibling, so this is implied rather than explicit guidance.

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

All BasketWatch tools Inspect

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

Need Help?