Skip to main content
Glama

apaxas

Entrar en un grupo

entrar_en_grupo
Idempotent

Use this when the user was sent the link or the code of an apaxas group and wants to join it. Joins as one of the people nobody has claimed yet or, if they are not listed, under the user's own name, like opening the link in the app. Without a name it does not join, and the reply says who is free. It cannot join as someone who is already in the group. Do not use it for a group the user is already in, or to start a new 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": {
      "grupo": "<grupo>"
    },
    "name": "entrar_en_grupo"
  }
}

Input Schema

NameRequiredDescriptionDefault
grupoYesThe group link (apaxas.com/k7m2qx9pr4tb), the message that brings it or its code, the end of the link. The group's name does not work here.
tu_nombreNoWho the user is in the group: one of the free names, or their own if they are not listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true) it discloses the actual join semantics: identity is claimed from unclaimed listed people, falls back to the user's own name, and the operation refuses without a name and refuses an identity already in the group. It also tells the agent what the reply contains ('says who is free'), which is the key behavioral detail for a mutation tool with no output schema.

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 trigger and identity rule, and every sentence carries operational information. Minor redundancy between 'It cannot join as someone who is already in the group' and 'Do not use it for a group the user is already in', which read similarly on first pass even though they concern identity vs. group membership.

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 two-parameter mutation tool with no output schema, the description covers trigger, identity resolution, failure modes, and reply content. The only soft spot is the phrase 'one of the people nobody has claimed yet', which leaves the agent to infer how to discover those free names before calling.

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 100%, so the schema already documents both fields, but the description adds real meaning on top: tu_nombre is effectively required in practice ('Without a name it does not join'), and grupo must be a link/code rather than the group's name. That conditional-requirement nuance is not derivable from the schema's 'required' list alone.

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 states a specific verb and resource (joining an apaxas group via link or code) and immediately scopes the identity behavior: joining as an unclaimed listed person or under the user's own name. It also draws the boundary against 'a group the user is already in' and against starting a new one, which separates it from ver_grupo/crear_grupo without needing the sibling schemas.

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 gives a clear triggering condition ('when the user was sent the link or the code') plus explicit exclusions (not a group already joined, not creating a new group). The alternative actions are described rather than named as tools, so the agent must map them to siblings itself.

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