wallos-mcp

Overview Schema Source Related Servers Discussions Admin

List subscriptions

list_subscriptions

Read-only

List Wallos subscriptions with prices, billing periods, and next payment dates. Filter by name, ID, category, member, or payment method to see what is paid or due.

Instructions

Lists the subscriptions in this Wallos account with their price, billing period and next payment date. Filters accept names or ids. This is the tool to reach for when asked what someone pays for, what is due, or what a category or person costs.

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": "list_subscriptions"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Sort order. Defaults to next_payment.
`state`	No	Defaults to "all".
`members`	No	Only subscriptions paid by these household members.
`all_users`	No	Return every user’s subscriptions instead of just this one. Admin (user id 1) only.
`categories`	No	Only these categories, by name or id.
`payment_methods`	No	Only these payment methods, by name or id.
`convert_currency`	No	Convert prices into the main currency using the current exchange rates.
`disabled_to_bottom`	No	Sort inactive subscriptions last.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 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=true and openWorldHint=true, so the safety profile is covered. The description still adds value by disclosing the return payload (price, billing period, next payment date) and the account scoping ("in this Wallos account"), which annotations do not convey.

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 sentences, each earning its place: purpose plus return fields first, filter flexibility second, selection guidance last. Front-loaded and free of filler.

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?

Eight optional parameters, no required fields, no output schema, and the description covers what comes back and when to use it; the schema itself handles every parameter and enum. Nothing an agent needs in order to call this correctly is missing.

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 coverage is 100%, with per-parameter descriptions and enums for sort and state, so the baseline is 3. The description's "Filters accept names or ids" restates what the schema already says for categories, members and payment_methods, adding no new syntax or edge-case detail.

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?

Names a specific verb and resource ("Lists the subscriptions") and immediately specifies the returned facts: price, billing period, next payment date. That is enough to distinguish it from get_subscription (single item) and get_monthly_cost (aggregate).

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 closing sentence gives explicit use cases — "what someone pays for, what is due, or what a category or person costs" — which maps directly to the filter parameters. It stops short of naming the sibling to use for a single subscription, so no hard exclusions, but the intent is clear.

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