Skip to main content
Glama
Sign In
Stables MCP Server

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List customer information requests

list_customer_rfis
Read-onlyIdempotent

Retrieve a customer's compliance requests for information (RFIs) and see what each requirement needs next, optionally filtered by status.

Instructions

List one customer's compliance requests for information (RFIs), with what each requirement needs next.

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_customer_rfis"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoOnly this status
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

B3.3/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the description does not need to repeat safety traits. It adds that results include 'what each requirement needs next,' which is useful behavioral context, but it says nothing about pagination, ordering, or result shape.

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?

It is a single front-loaded sentence with no filler. The core action and scope are stated immediately, and the phrase about next requirements adds a useful detail without surplus wording.

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

Completeness3/5

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

For a two-parameter read-only list tool with rich annotations and full schema coverage, the basics are covered. However, with no output schema, the description should say more about what the returned RFIs and 'needs next' fields look like, plus whether results are 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%, so customerId and the status enum are already fully documented. The description reinforces that the list is scoped to one customer, but adds no syntax, filtering semantics, or enum meaning beyond the schema.

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 description gives a specific verb and resource: listing a single customer's compliance requests for information. The scoping phrase 'one customer's' distinguishes it from the broader sibling list_rfis, though it does not name that sibling explicitly.

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

Usage Guidelines2/5

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

Usage is only implied by the requirement of a customer ID. The description never says when to use this rather than list_rfis, get_rfi, or submit_rfi_evidence, so an agent gets no explicit routing guidance.

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