Skip to main content
Glama

apaxas

Crear un grupo

crear_grupo

Use this when the user wants to split costs with other people (a trip, a shared flat, a couple, a dinner, any shared plan) and has no apaxas group for it yet. Creates the group with the user in it and the others by name and, if the user already said what was spent, logs those expenses in the same call. Returns the group link, which the user sends to the others so each one opens it and says who they are. It also works without an apaxas account: then the user's name is needed, and the reply brings a key to keep using this group from this conversation. With the account, calling it again right away with the same name does not create a second group or log the expenses twice. Do not use it when the user already has a group for this plan or was sent the link to one.

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": {
      "nombre": "<nombre>"
    },
    "name": "crear_grupo"
  }
}

Input Schema

NameRequiredDescriptionDefault
gastosNoOptional: the expenses the user has already mentioned, to log them in the new group. The names are the user's and those in «personas».
monedaNoISO 4217 code of the currency the group keeps its accounts in (EUR, USD, GBP…). EUR if not given.
nombreYesThe group's name: «Lisboa», «Piso de Lavapiés», «Marta's birthday».
personasNoThe other people in the group, without the user, by the name everyone knows them by.
tu_nombreNoThe user's name in this group, the one the others know them by. Needed without the user's apaxas account; with it, the name on the account if not given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations: discloses the anonymous path (name required, key returned to continue in the same conversation), the returned group link and how the user shares it, and optional expense logging in the same call. One tension worth noting: it says calling again right away with the same name "does not create a second group or log the expenses twice", while idempotentHint=false implies no such guarantee — the scoped wording (same name, right away) reads as a dedup guard rather than a blanket claim, but an agent could over-rely on it.

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 use case, then behavior, then the exclusion; every sentence carries distinct information (return value, no-account path, dedup). It runs long and the multi-clause sentences take a second read, but nothing is pure filler.

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 create tool with no output schema, the description still covers what comes back (group link, and the key for the anonymous flow), both auth paths, and the duplicate-call behavior. Combined with the fully documented nested expense schema, an agent has everything needed to call it correctly.

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% and the nested expense schema is thoroughly documented, so the schema does most of the work. The description adds only two things beyond it: that the user is added to the group automatically (hence not in "personas") and that expense names refer to the user and to "personas". Baseline 3 is right here.

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?

Names a specific verb and resource ("Creates the group with the user in it") and immediately scopes it to the cost-splitting scenario (trip, flat, couple, dinner). It also differentiates from siblings by refusing the case where "the user already has a group for this plan or was sent the link to one", which is exactly what entrar_en_grupo/ver_grupo cover.

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?

"Use this when..." plus an explicit "Do not use it when..." exclusion give a clear selection rule, including the precondition of having no group yet. The alternative tools are described by situation rather than named, so the routing is inferable but not spelled out by name.

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