Skip to main content
Glama

shared_expenses_split

Shared expenses: splits each expense by the agreed percentages (50/50, 60/40, 70/30…), totals by category and who owes whom. Price: $0.005 USDC per call (x402).

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": {
      "expenses": "<expenses>"
    },
    "name": "shared_expenses_split"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the core texts (default it)
currencyNo
expensesYes
parent_aNo
parent_bNo
default_share_aNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose a genuinely useful behavioral trait: a $0.005 USDC charge per call under x402, implying a payment handshake the agent must be prepared for. It also previews the output content (per-category totals, settlement direction). However, it says nothing about whether anything is stored, whether the call is repeatable without cost side effects, or how partial shares are rounded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the operation and its outputs, then the cost. The percentage parenthetical is illustrative rather than required but is short and clarifies the share model. Little waste overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter tool with no annotations and no output schema, the description is thin: the highest-risk part, the structure of each element in the required expenses array, is completely undocumented, as are the roles of parent_a and parent_b. An agent can guess the intent but not how to build a valid call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17% across six parameters, so the description must compensate and largely fails to. The percentage examples (50/50, 60/40, 70/30) hint at default_share_a, but parent_a, parent_b, currency, lang, and especially the untyped expenses array items receive no explanation of expected shape or meaning anywhere.

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 a specific operation (splitting shared expenses by agreed percentages) and states the outputs produced (category totals and who-owes-whom), which goes beyond restating the name. It does not need sibling differentiation since no listed sibling performs expense splitting, but the wording is compressed enough that the exact input unit (a list of expenses plus two parents' shares) must be inferred.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus any alternative, no prerequisites or preconditions, and no statement of whether the tool merely calculates or also persists records. The only usage-relevant statement is the per-call price, which is a cost note rather than a when-to-use rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources