Skip to main content
Glama
Sign In
wallos-mcp

wallos-mcp

by LovelessCodes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Manage a category

manage_category
Destructive

Add, rename or delete spending categories; Wallos blocks deletion while subscriptions still use the category and names the conflicting subscriptions.

Instructions

Adds, renames or deletes a spending category. Wallos refuses to delete a category that subscriptions still use, and will name the ones in the way.

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": {
      "action": "<action>"
    },
    "name": "manage_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe entry to edit or delete, by name or id. Required for edit and delete, ignored for add.
nameNoCategory name: the new one for add and edit.
actionYesWhat to do: add a new entry, edit an existing one, or delete it.

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?

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: a referential-integrity guard on delete and a failure mode that names the blocking subscriptions, which is exactly what an agent needs to recover from an error.

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, no filler. The operation set is front-loaded and the delete constraint follows immediately, so the most important risk information is read first.

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 three-action mutation tool with full schema coverage and destructive annotations, the description covers the risky path and its failure behavior. It omits whether edit requires both id and name, but the schema closes that gap.

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%, so id/name/action semantics are already documented in structured fields. The description adds only the field-level mapping of 'renames' to what the schema calls 'edit', which is a marginal contribution at baseline level.

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?

States specific verbs (adds, renames, deletes) against a specific resource (spending category), which is enough to separate it from the subscription-oriented siblings and from manage_currency/manage_payment_method/manage_household by resource. It stops short of explicitly naming an alternative, but the resource is unambiguous.

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 by the three verbs and the delete precondition ('refuses to delete a category that subscriptions still use') tells the agent when delete will fail. There is no explicit statement of when to choose this tool over a sibling, nor guidance tying actions to required parameters.

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