Skip to main content
Glama

apaxas

Apuntar gastos

apuntar_gastos

Use this when the user says what someone paid or wants to add costs to an existing apaxas group («dinner was 86 euros, I paid», «Ana paid the taxi»), including a repayment between two people or money the group received. Logs one or several entries on the user's behalf, only to work out who owes whom. Names must be people in the group; if one is not, the reply lists them. All or nothing: if anything is wrong, nothing is logged and the reply says what to fix. Up to 50 at once. The others in the group get a phone notification. Do not use it to pay, send or request money: apaxas never moves money.

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": {
      "grupo": "<grupo>",
      "gastos": "<gastos>"
    },
    "name": "apuntar_gastos"
  }
}

Input Schema

NameRequiredDescriptionDefault
grupoYesThe group's code, the end of its link. Its name or its link also work.
llaveNoThe key that came with this group when it was created without an apaxas account. Not needed when the user's account is connected.
gastosYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint=false / destructiveHint=false annotations: all-or-nothing atomicity, a 50-entry batch cap, phone notifications to other members, member-name validation with names echoed in the error reply, and the fact that no funds move. These are operational traits an agent cannot derive 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-loads the trigger condition and examples, then layers constraints in short, dense sentences with no filler. It runs somewhat long, but each clause (atomicity, cap, notifications, member validation, no money movement) carries distinct information.

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?

There is no output schema, and the description partly compensates by describing what the reply contains on failure (the offending names, what to fix). It does not describe the success response at all, which leaves a small gap for a tool whose main output is a confirmation.

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?

Schema coverage is 67% and the nested fields (tipo, para, partes, cantidades, pagador) are already well documented in the schema. The description still adds real constraint semantics: persona values must be people in the group, otherwise nothing is logged and the reply lists the offenders. It adds little about grupo/llave beyond what the schema says.

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 and resource: logging expense/repayment/income entries into an existing apaxas group, with quoted user-utterance triggers. It also draws a hard boundary ('Do not use it to pay, send or request money'), which separates it from payment-oriented tools and from the group-creation siblings.

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

Usage Guidelines5/5

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

Gives explicit when-to-use criteria ('when the user says what someone paid or wants to add costs to an existing apaxas group'), concrete example phrasings, and an explicit when-not ('never moves money'). The word 'existing' implicitly tells the agent the group must already exist, which routes creation to crear_grupo.

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