Skip to main content
Glama

Get a payment link for a new domain

solicitar_dominio
Idempotent

Use this when the person wants a new domain name (e.g. panaderia-ruzafa.es) for their palimpalem website. Requires palimpalem sign-in. Checks that the name is free and returns a payment link on palimpalem.com with the price. On that page the person enters the details of the domain owner (always the person or their business) and pays; the domain is registered after payment. This tool registers nothing and charges nothing.

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": {
      "domain": "<domain>"
    },
    "name": "solicitar_dominio"
  }
}

Input Schema

NameRequiredDescriptionDefault
webNoOptional when the account has one website. The website the domain is for.
domainYesThe full domain name with ending, e.g. panaderia-ruzafa.es. Endings: com, es, net, info, org, de, eu.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, it discloses authentication requirements, that the name is checked for availability, that the output is a payment link with the price, and that the human completes owner details and payment on the external page. Crucially it states 'This tool registers nothing and charges nothing,' bounding the side effects — context the annotations (readOnlyHint=false, openWorldHint=true) alone do not 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?

Three tightly packed sentences: the trigger first, then prerequisites and outcome, then an explicit negative-scope disclaimer. No filler, and the most decision-relevant clause leads.

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?

For a two-parameter tool that hands off to an external payment flow with no output schema, the description covers everything an agent needs: when to call, auth, what the return is, what the human does next, and that no charge or registration occurs on the call itself.

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 description coverage is 100%, so both the domain format/endings and the optional 'web' parameter are already documented. The description adds only the example domain and the clarification that the owner is always the person or their business, which is marginal beyond the schema. Baseline 3 applies.

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?

States a concrete verb and resource — obtaining a payment link for a brand-new domain on a palimpalem website — and the example 'panaderia-ruzafa.es' pins the artifact. The emphasis on 'new domain name' implicitly separates it from availability-check and existing-domain siblings, and the closing line clarifies it is not a registration tool.

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 a new domain name ... for their palimpalem website' gives an explicit trigger condition plus the prerequisite of palimpalem sign-in. It does not name alternatives (e.g. connecting an existing domain) or state when not to use it, so guidance is clear but not fully routed.

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.