Skip to main content
Glama

username_search

Check whether a username exists across ~25 platforms, optionally limiting sites. Results separate found, not found, and blocked so Cloudflare 403s are not mistaken for absence.

Instructions

Check whether a username exists on ~25 platforms (GitHub, GitLab, Reddit, Telegram...).

sites optionally limits checks to comma-separated keys. Results distinguish found / not found / blocked, so Cloudflare 403s are not reported as absence.

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": {
      "username": "<username>"
    },
    "name": "username_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sitesNo
timeoutNo
usernameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/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 disclose a non-obvious trait: results distinguish found / not found / blocked so Cloudflare 403s are not misreported as absence. That is exactly the kind of behavioral detail an agent could not get from structured fields. It omits rate limiting, request cost/latency, and whether the checks run in parallel, which keeps it from a 5.

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, front-loaded with the core action and followed by the parameter hint and the results caveat. No filler, no repetition of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations and no output schema, describing the three-way result taxonomy is a genuinely useful completeness win. However, with 0% schema coverage the definition leaves the agent guessing on valid `sites` keys and on `timeout` units, both of which matter before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 3 parameters. The description only gives meaning to `sites` ('comma-separated keys'), and even there it never states what valid keys are or where to get them. `timeout` (default 12, units unstated) and `username` receive no explanation at all, so the compensation for the zero-coverage schema is thin.

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 opens with a specific verb and resource — 'Check whether a username exists' — and scopes it to '~25 platforms (GitHub, GitLab, Reddit, Telegram...)', which implicitly separates it from single-source siblings like github_search or bluesky_profile. It is clear without an explicit sibling comparison, so a 4 rather than a 5.

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 use case (enumerating account presence for a handle) is implied by the wording, and the `sites` sentence hints at the narrow-scan variant, but there is no explicit 'use this when…, use X instead when…' guidance and no stated prerequisites. An agent can infer the fit, but nothing is spelled out.

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