Skip to main content
Glama
Sign In
wallos-mcp

wallos-mcp

by LovelessCodes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get one subscription

get_subscription
Read-only

Retrieve a single subscription by ID, including its category, payer, and payment method names, to view subscription details and optionally convert the price to the main currency.

Instructions

Reads a single subscription by id, including its category, payer and payment method names.

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": {
      "id": "<id>"
    },
    "name": "get_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSubscription id, as returned by list_subscriptions.
convert_currencyNoConvert the price into the main currency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With readOnlyHint=true and openWorldHint=true already provided, the description adds useful context by naming some returned fields (category, payer, payment method names). It does not mention error behavior, permissions, or rate limits, but for a simple read operation this is fairly transparent.

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?

The description is a single front-loaded sentence with no filler. Every phrase adds useful information: verb, resource, identifier, and included fields.

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 low-complexity read tool with rich schema coverage and safety annotations, the description is nearly complete. It partially explains return content, though without an output schema it could be more explicit about what else is returned or what happens when the id is not found.

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 both parameters are already documented in the schema. The description only adds 'by id' and does not elaborate on convert_currency or id formatting beyond schema content, making the baseline 3 appropriate.

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 states a specific verb ('Reads') and resource ('a single subscription by id'), clearly distinguishing it from list_subscriptions. It also names included fields (category, payer, payment method names). However, it does not explicitly contrast with sibling tools such as get_monthly_cost or get_period_budget, so it falls short of perfect differentiation.

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 implied: call it when you have a subscription id and need one record. The description does not explicitly say when not to use it or name alternatives like list_subscriptions for broader retrieval, so guidance is minimal but adequate.

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