Skip to main content
Glama

apaxas

Ver un grupo

ver_grupo
Read-onlyIdempotent

Use this when the user asks how a group's shared expenses stand: who owes whom, how much someone owes or is owed, how to settle up or what has been spent lately. Shows one apaxas group: what each person owes or is owed, the payments that would even everyone up and the latest expenses.

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>"
    },
    "name": "ver_grupo"
  }
}

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.
gastosNoHow many of the latest expenses to include (30 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?

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful output semantics—per-person balances, settlement payments, and recent expenses—though it omits edge cases such as missing groups or detailed pagination behavior for the expense list.

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?

Two sentences, front-loaded with usage guidance and then output scope; there is no redundant restatement of the title or annotations.

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?

For a three-parameter read-only tool with full schema descriptions and annotations, the definition covers the essential purpose and return content. It could be stronger on failure cases or group access requirements, but nothing critical is missing.

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%, with descriptions for grupo, llave, and gastos, so the schema carries the parameter meaning. The description only alludes to 'latest expenses' and adds no syntax, defaults, or constraints beyond what the schema provides.

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 names a specific read operation ('Shows one apaxas group') and enumerates the content returned: balances, settlement payments, and latest expenses. The word 'one' implicitly distinguishes it from the plural group-listing sibling ver_grupos.

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?

It supplies concrete trigger questions ('who owes whom', 'how to settle up', 'what has been spent lately'), giving clear when-to-use guidance. It does not name alternatives or state when not to use it, so it falls short of the full 5.

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