Skip to main content
Glama
Club Alpin MCP

Club Alpin MCP

by jalmeida17

get_my_registrations

Read-onlyIdempotent

Retrieve your upcoming Club Alpin outings where you have a registration, including your status, role, organizer flag, dates, meeting point, and overlap warnings.

Instructions

My upcoming outings, as on the site page "Profil : mes sorties à venir" (needs CLUB_ALPIN_EMAIL / CLUB_ALPIN_PASSWORD): every published outing not finished yet where I have a registration, with my_status ("accepted", "pending" = waiting for the organizer, "refused", "absent"), my_role (participant, encadrant, co-encadrant...), i_am_organizer, start/end, availability, url, and under untrusted_member_text the title, meeting point and warnings about overlapping outings. Use get_sortie for the detail. Read-only: this server cannot register nor unregister you.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_my_registrations"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only annotations, it discloses authentication requirements, the exact status/role fields returned, the untrusted_member_text wrapper, overlap warnings, and states that the server cannot register or unregister users. This adds substantial behavioral context not present in 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?

The purpose is front-loaded and every segment adds useful information, including auth requirements, returned fields, and the get_sortie alternative. It is somewhat dense and run-on, but not padded or wasteful.

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?

With no output schema, the description compensates by naming the returned fields and describing the untrusted_member_text content. It also covers auth and the read-only limitation, making the definition complete for this zero-parameter tool.

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?

The tool has zero parameters, so there are no parameter semantics to explain. The baseline for a no-parameter tool is 4, and the description appropriately spends its space on output and usage context instead.

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 resource and scope: upcoming published outings that are not finished and where the user has a registration. It distinguishes itself from get_sortie by saying that tool is for detail, so an agent can select it confidently.

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 clearly frames the use case as retrieving the user's own upcoming registrations and explicitly points to get_sortie for detailed outing information. It does not explicitly compare against list_sorties or get_my_history, so the sibling differentiation is useful but not exhaustive.

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