Skip to main content
Glama
Sign In
Stables MCP Server

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List available entitlements

list_available_entitlements
Read-onlyIdempotent

Retrieve a customer's unapplied entitlements to see available products and payment rails, current eligibility, and the verification each requires.

Instructions

List the entitlements (products and payment rails, e.g. 'aed_local') a customer has not applied for yet, whether each is available to them now, and the verification it needs.

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": {
      "customerId": "<customerId>"
    },
    "name": "list_available_entitlements"
  }
}

Input Schema

NameRequiredDescriptionDefault
customerIdYesThe customer ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.6.11
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv2.4.0

TDQS

A3.9/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 description's job is to add content-level behavior — which it does by declaring that each entry reports current availability and required verification. With no output schema, that is genuinely useful disclosure. It stops short of mentioning ordering, pagination, or what an empty list means.

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 front-loaded sentence with no filler, and the resource definition precedes the qualifier. The trailing clause ('whether each is available to them now, and the verification it needs') is slightly dense but each element carries real information.

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?

With no output schema, the description must shape expectations about the return payload, and it does — listing per-entitlement availability and verification requirements. For a one-parameter read tool this is close to complete; only result ordering and emptiness semantics are unaddressed.

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?

One parameter with 100% schema coverage, so the schema already fully documents customerId. The description only reinforces that results are scoped to a single customer; it adds no format, validation, or edge-case detail beyond the schema. Baseline 3 applies.

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?

Specific verb ('List') plus a clearly scoped resource ('entitlements'), with a concrete example value ('aed_local') and an explicit disambiguator: these are entitlements the customer has *not* applied for yet. That distinguishes it from the write-side siblings request_entitlements and submit_entitlement_requirements without needing the schemas.

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 'has not applied for yet' qualifier implies the use case (pre-flight check before applying), but the description never says when to call it versus request_entitlements or submit_entitlement_requirements, nor any precondition such as the customer already existing or being KYC'd. Usage is inferable but not stated.

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

Deploy Server

Other Tools