Skip to main content
Glama

Empezar con Wyro

wyro_empezar

Úsala primero cuando el usuario acaba de instalar Wyro o pregunta qué puede hacer, cómo funciona o cuánto cuesta: devuelve el estado y qué explicarle. Si todavía no hay clave, crea una de prueba gratis (sin registro).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool returns status and explanation guidance, and that it may create a free trial key without registration, which is useful. However, it does not state whether key creation is idempotent, what happens if a key already exists, or any rate limits or permission requirements.

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?

The description is a single, front-loaded sentence that moves efficiently from usage triggers to return value to side effect. Every clause earns its place, with no repetition or filler.

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?

Given the low complexity (zero parameters, no output schema), the description is nearly complete: it covers when to use the tool, what it returns, and that it may create a trial key. Minor gaps remain around the exact shape of the returned status and any constraints on key creation, but these are not critical for an onboarding 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 per the rubric the baseline is 4. The description adds no parameter semantics, but none are needed, and it does not introduce confusion about inputs.

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 onboarding purpose: use first when the user has just installed Wyro or asks what it can do, how it works, or how much it costs. It also clarifies that the tool returns status and explanation guidance, and may create a free trial key. However, it does not explicitly name sibling tools or contrast itself with them beyond the 'use first' cue.

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 gives clear triggering conditions: just installed Wyro, asks what they can do, how it works, or how much it costs. The word 'primero' implies precedence, but no explicit exclusions or named alternatives are provided, so the guidance is strong but not exhaustive.

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.