Skip to main content
Glama

Get a payment link for Plus

solicitar_plus
Idempotent

Use this when the person wants the paid Plus service for their palimpalem website, which keeps it online without limits after the free trial. Requires palimpalem sign-in. Returns a payment link on palimpalem.com with the price; the person pays there. 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_plus"
  }
}

Input Schema

NameRequiredDescriptionDefault
webNoOptional when the account has one website.
billingNoPay per year or per month. The person can still switch on the payment page.yearly

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?

The description adds context the annotations cannot carry: an authentication requirement, the fact that the tool only returns a price-bearing link on palimpalem.com, that payment happens off-tool by the human, and explicitly that 'this tool charges nothing.' That last point directly resolves the ambiguity created by readOnlyHint=false (an agent might otherwise fear the tool performs a charge), and it is plain from the text that the operation is non-destructive.

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?

Four short sentences, each carrying distinct information in priority order: trigger, auth prerequisite, what is returned, and the no-charge assurance. No filler or repetition, and the most decision-relevant clause comes first.

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-optional-parameter tool with no output schema, the description covers everything needed to call it correctly: the trigger condition, the sign-in requirement, the fact that the return value is a payment link containing the price, and that the user must complete payment externally. Return-value explanation is present where the output schema is absent.

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 parameters (web, billing) are already fully documented, including the 'Optional when the account has one website' note and the yearly default with a switch-on-page note. The description only alludes to the website in passing ('for their palimpalem website') and never mentions the billing period, which is acceptable given the schema but adds no extra meaning beyond it.

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 specific verb and resource: requesting a payment link for the paid Plus service for a palimpalem website. It is immediately distinguishable from the siblings (solicitar_correo, solicitar_dominio, publicar_web) because it names the paid plan and the deliverable (a link on palimpalem.com), not an email, domain, or publishing action.

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?

Gives an explicit trigger ('Use this when the person wants the paid Plus service... which keeps it online without limits after the free trial') and a precondition (requires palimpalem sign-in). It does not name alternatives or state when not to use it, so it stops short of full routing guidance, but the positive condition is unambiguous enough for selection.

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.