Skip to main content
Glama

OLA Vital Center

Empezar el registro

ola_iniciar_alta
Read-onlyIdempotent

Da el enlace para que la persona se registre y pague su membresía ella misma en la app de OLA. No crea cuentas ni cobra: no le pidas datos personales ni de tarjeta, solo compártele el enlace.

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": "ola_iniciar_alta"
  }
}

Input Schema

NameRequiredDescriptionDefault
nivelNoNivel que le interesa, si ya lo dijo.

Output Schema

NameRequiredDescriptionDefault
enlaceYes
cobradoYes
siguienteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description still earns credit for adding non-obvious context: it creates no account, charges nothing, and the agent must not collect PII or card data – a real behavioral constraint an agent could otherwise violate. It stops short of describing the link's lifetime or whether it is per-person.

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 short sentences, with the primary action stated first and the guardrail second; nothing is redundant or padded. The negative framing is compact and front-loaded exactly where an agent needs it.

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?

The tool is simple, an output schema exists for the return value, and annotations cover safety, so the description only needs purpose plus behavior – both delivered. The one small gap is that it doesn't mention the optional nivel parameter that can shape the link.

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?

With 100% schema description coverage and a single optional parameter whose enum values (brisa/ola/marea) are self-describing, the schema carries the parameter burden and the baseline of 3 applies. The description adds nothing about the nivel parameter, not even that it is optional and should only be passed if already known.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Da el enlace para que la persona se registre y pague su membresía" states a concrete verb (deliver a link) and a concrete outcome (self-service registration and payment), and the negative clause ("No crea cuentas ni cobra") further pins down the behavior. It does not name or contrast the sibling tools, so the differentiation is behavioral rather than explicit.

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?

The when-to-use condition is clear from "para que la persona se registre y pague" – the agent should reach for this when someone wants to sign up and pay on their own. It also gives an explicit operating rule ("no le pidas datos personales ni de tarjeta, solo compártele el enlace"), which is actionable guidance, but it never names an alternative tool or an exclusion case.

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