Skip to main content
Glama

Get a payment link for e-mail

solicitar_correo
Idempotent

Use this when the person wants e-mail addresses with their own domain (e.g. info@their-domain.es) for their palimpalem website. Requires palimpalem sign-in. Without a package it lists the packages with mailboxes, storage and price; with a package it returns a payment link on palimpalem.com. Mailboxes are created after payment. This tool charges nothing.

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

Input Schema

NameRequiredDescriptionDefault
webNoOptional when the account has one website.
domainNoOptional when the website has one domain. The domain for the addresses.
packageNoThe e-mail package. Leave empty to see the packages first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (which only say readOnly=false, openWorld=true, idempotent=true, destructive=false), the description discloses the sign-in requirement, the no-charge behavior, the two distinct response modes, that the link is hosted on palimpalem.com, and that mailboxes only exist after payment. That is exactly the operational context the annotations cannot convey.

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?

Five short sentences, front-loaded with the trigger, then prerequisite, then behavior, then outcome. No filler and no restatement of the title or name.

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?

With no output schema, the description does the necessary work of describing both possible return shapes (package listing vs. payment link). The remaining gap is preconditions on `domain`: it doesn't say whether the domain must already be registered or connected via a sibling tool before requesting mailboxes.

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 baseline is 3; the description still adds value by explaining the consequence of omitting `package` (a listing of packages with mailboxes, storage and price) rather than just describing the field. It adds no detail on `web`/`domain` beyond what the schema already says.

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?

The description states a specific resource (e-mail addresses on the customer's own domain for a palimpalem website) and a specific outcome (a payment link on palimpalem.com), and its dual behavior (listing packages vs. returning a link) is spelled out. It distinguishes itself implicitly from domain-purchase siblings by being about mailboxes, but never names an alternative, so an agent must infer the boundary.

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 the person wants e-mail addresses with their own domain" gives a clear trigger condition, and "Requires palimpalem sign-in" states a prerequisite. It does not say when NOT to use it or point to a sibling (e.g. for buying/connecting the domain itself), leaving that routing to inference.

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.