Skip to main content
Glama
Sign In
wallos-mcp

wallos-mcp

by LovelessCodes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Manage a household member

manage_household
Destructive

Add, edit, or delete household members used to attribute subscriptions; deletion is blocked while subscriptions remain assigned.

Instructions

Adds, edits or deletes a household member. Members are who subscriptions are attributed to, not login accounts. Wallos refuses to delete a member that subscriptions are still attributed to.

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

Input Schema

NameRequiredDescriptionDefault
idNoThe entry to edit or delete, by name or id. Required for edit and delete, ignored for add.
nameNoMember name. Required for add.
emailNoMember email, used when Wallos emails them about their subscriptions.
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

A4/5.0
Behavior4/5

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

The annotations already declare destructive, open-world, and non-idempotent behavior, and the description adds key domain behavior beyond that: members are attribution subjects, not login accounts, and deletion is refused while subscriptions are still attributed to the member. It does not cover permissions or response behavior, but it adds meaningful operational context.

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 three tight sentences: purpose first, conceptual distinction second, deletion constraint third. Every sentence adds useful information without redundancy.

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?

The schema fully documents the four parameters and the annotations cover safety profile, so the description is complete enough for correct invocation. It could add a bit more detail about edit behavior or partial updates, but nothing critical is missing for an agent to choose and call the tool.

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 the parameters are fully documented in the schema already. The description adds conceptual meaning about members and subscription attribution, but it does not add per-parameter detail beyond the schema, so the baseline 3 is appropriate.

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?

The description states a specific CRUD verb set and resource: 'Adds, edits or deletes a household member.' It also distinguishes household members from login accounts and explains that subscriptions are attributed to them, which prevents confusion with account-related siblings.

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?

The action enum and schema make usage implicit, and the deletion constraint is helpful context. However, the description does not explicitly say when to use this tool versus related resource-management tools such as update_subscription or manage_category.

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