Skip to main content
Glama
Sign In
wallos-mcp

wallos-mcp

by LovelessCodes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get categories, currencies, payment methods and household

get_master_data
Read-only

Retrieve all subscription reference data—categories, currencies, payment methods, and household members with IDs—before creating or updating subscriptions so names match existing records.

Instructions

Everything a subscription can point at, in one call: categories, currencies with the main one flagged, payment methods and household members, each with its id. Call this before changing a subscription so the names you pass are real, and to answer questions about how someone organises their spending.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 safety is covered. The description adds real value beyond that by disclosing return contents (each entity carries its id, the main currency is flagged) and framing it as a single batch call, which matters since there is no output schema.

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?

Two sentences with no waste. What is returned is front-loaded, followed by the actionable guidance, which is exactly the right ordering for an agent.

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 and no parameters, the description carries the burden of describing the response, and it enumerates all four entity types plus the main-currency flag. Minor gap: it does not state the response envelope (single object vs separate collections) or whether any of the collections can be empty.

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 zero parameters, so the baseline is 4. The description correctly implies no inputs are needed by describing it as 'everything ... in one call', which is the right level of parameter guidance here.

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 names the exact resources returned (categories, currencies with main flagged, payment methods, household members) and states the read-only intent implicitly through 'call this before changing'. It is clearly separable from the manage_* siblings, though it never names them explicitly.

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?

Two concrete usage conditions are given: resolve real names before mutating a subscription, and answer questions about spending organisation. There is no when-not guidance or explicit pointer to the manage_category/manage_currency alternatives for writes.

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