Skip to main content
Glama

Partly Exact Split

Server Details

Split expenses in cents with equal/weighted shares and payer advances. No account or payments.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.7/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is no risk of selecting the wrong tool or confusing it with another operation. Its purpose is clearly scoped to shared-expense balance calculation.

Naming Consistency5/5

The single tool name follows a clear verb_noun snake_case convention: calculate_shared_expenses. With only one tool, there is no inconsistent naming pattern to create confusion.

Tool Count4/5

The server is narrowly focused on a stateless expense-splitting calculator, so one tool is reasonable rather than obviously incomplete. However, a single tool is thinner than the typical 3–15 tool range and leaves little room for complementary operations.

Completeness5/5

For the stated stateless calculation purpose, the tool covers participants, expenses, payers, equal and weighted shares, multiple currencies, and reimbursement suggestions. It explicitly clarifies that storage, account access, and transfers are out of scope, so there are no apparent dead ends within its domain.

Available Tools

1 tool
calculate_shared_expensesCalculate exact shared expensesA
Read-onlyIdempotent
Inspect

Calculate balances and reimbursement suggestions for 2–30 participants across 1–100 expenses with different payers and equal or weighted shares. Uses integer cents, deterministic largest-remainder allocation, and offsets debts. Supported single currencies: EUR, USD, GBP, CHF, CAD; no conversion. The tool is stateless and cannot access accounts, fetch data, store results or transfer money. Use aliases when possible.

NameRequiredDescriptionDefault
currencyYes
expensesYes
participantsYes

Output Schema

NameRequiredDescription
currencyYes
transfersYes
totalCentsYes
participantsYes

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description still adds substantive behavior: statelessness, no persistence, no transfers, deterministic largest-remainder allocation, integer-cent arithmetic, and debt offsetting. These are outcome-shaping traits an agent could not infer from the schema or annotations.

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?

Front-loaded with the core action and constraints, then behavioral limits, then a short practical tip; nearly every clause carries information. The closing 'Use aliases when possible' is slightly vague about which field it targets.

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

Completeness5/5

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

For a pure computation tool with a full output schema, everything needed to call it correctly is present: input bounds, currency restriction, rounding model, and the fact that it neither reads nor writes external state. Return values are correctly left to the output schema.

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?

Nested schema descriptions exist but top-level coverage is reported low, and the description compensates by explaining equal-vs-weighted share semantics, cent-based amounts, participant/expense count bounds, and the exact supported currency set. It stops short of naming individual parameter fields, leaving field-level detail to the schema.

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?

States a specific verb+resource ('calculate balances and reimbursement suggestions') and immediately bounds it: 2–30 participants, 1–100 expenses, equal or weighted shares. The scope is unmistakable even without siblings to compare against.

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?

Gives clear operating context — stateless, no account access, no data fetching or storage, no money transfer, single currency with no conversion — which tells an agent what cannot be delegated here. It lacks an explicit when-to-use/when-not framing, but with no sibling tools there is little alternative routing to specify.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedcalculate_shared_expenses

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    Runs an entire shared-expense split from an assistant: create one, add what each person paid (equally, by weighted shares or exact amounts), record paybacks, and read back who owes whom as the fewest transfers. Eleven tools covering the whole lifecycle, with no account and no API key — people are referred to by name and amounts are plain decimals, so an agent never handles uuids or cents.
    4
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables group expense management and fair settlement via MCP, allowing creation of groups, recording expenses, viewing balances, and computing minimal transfers to settle debts.
    8
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI assistants to manage Splitwise expenses with atomic duplicate prevention, smart fuzzy matching, and support for flexible split ratios between two people.
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources