Skip to main content
Glama

Conectar una cuenta real

wyro_conectar_cuenta

Devuelve el link para conectar la cuenta real de una red y cómo acompañar al usuario en el proceso (qué cambia, qué va a ver, requisitos de la red, qué hacer si algo falla). Úsala cuando quiera publicar de verdad o después de un post simulado que le gustó. La clave actual sigue funcionando: no hay que reconfigurar nada.

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": {
      "red": "<red>"
    },
    "name": "wyro_conectar_cuenta"
  }
}

Input Schema

NameRequiredDescriptionDefault
redYesRed a conectar, por ejemplo instagram.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a decent job: it discloses that the tool returns a link rather than connecting itself, enumerates what the user will experience, covers failure handling, and explicitly reassures that the existing key still works without reconfiguration. It does not address link expiry, idempotency of repeated calls, or any permission/auth requirements for the calling environment.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: what it returns, when to use it, and the reassuring prerequisite about the key. The key reassurance is placed last rather than front-loaded, but nothing is redundant or padded.

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?

There is no output schema, so the description correctly compensates by describing the return payload (link plus step-by-step guidance). For a one-parameter link-generation tool this is close to complete; only edge cases like expired or reused links are unaddressed.

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?

The single `red` parameter has a 100% schema description and a closed enum of eight networks, so the schema fully documents it. The description adds no meaning beyond that (e.g., defaults, behavior for unsupported networks), so the baseline of 3 applies.

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 concrete verb and artifact: it returns the link to connect a real account on a given network, plus accompanying guidance (what changes, what the user will see, network requirements, failure handling). This clearly distinguishes it from wyro_publicar and wyro_cuentas, though it never names those siblings explicitly.

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?

Usage is stated clearly: use it when the user wants to actually publish or after a simulated post they liked. That gives the agent a positive trigger. It lacks an explicit when-not clause or a direct pointer to the sibling tool to use instead (e.g., staying in simulated mode), which keeps it below a 5.

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.