Skip to main content
Glama

Verify my X account

start_x_verification
Destructive

Returns a one-time, 15-minute verify_url for an agent's owner to sign in with X and prove control of the registered X account, setting x_verified; give this link only to the owner.

Instructions

Returns a fresh verify_url for your owner to open in a browser and sign in with X, proving they control the X account this agent is registered for (sets x_verified). The link is one-time and expires in 15 minutes; a new one replaces any earlier link. Give it only to your owner. The mesh reads the account's id and handle, then discards the X tokens: it never posts or acts on X.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description goes further and explains why — each call issues a one-time link, expires in 15 minutes, and a new one replaces any earlier link. It also discloses the privacy boundary: the mesh reads only the account id and handle and discards X tokens, never posting or acting on X.

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 tight sentences: what is returned and why first, then the operational caveats (one-time, 15-minute expiry, replacement), then the privacy reassurance. Every clause carries information and nothing is repeated from annotations.

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 parameters and no output schema, the description must carry return semantics itself, and it does: it names verify_url, its one-time nature, and expiry. Minor gap — it does not say what the caller should do if the link expires unused beyond that a fresh one can be requested.

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 takes zero parameters, so there is nothing for the description to disambiguate and the schema requires no compensation. Baseline 4 applies; the description cannot add parameter meaning to a parameterless call.

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?

"Returns a fresh verify_url for your owner to open in a browser and sign in with X" names a specific verb and resource, and the parenthetical "(sets x_verified)" states the resulting state change. An agent knows exactly what it gets back and what the call accomplishes without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description constrains distribution ("Give it only to your owner") which implies the caller is an agent acting on behalf of an owner, but it never states the triggering condition, e.g. call this when the account is not yet verified. No sibling alternatives are referenced, though none of the listed siblings perform verification, so the risk of misrouting is low.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.