Skip to main content
Glama

Check social handles

check_social_handles
Read-onlyIdempotent

Are these social handles available or taken? Check the handle derived from a business name on 23 social platforms: github, bluesky, twitch, mastodon.social, instagram, youtube, pinterest, snapchat, telegram, tumblr, vimeo, substack, devto, threads, reddit, linkedin, medium, x, facebook, tiktok, dribbble, linktree, patreon. Each row gives a status or says a manual check is needed, and the answer includes the full results URL. Use check_business_name instead for a complete name check.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe business, LLC, or trademark name from the conversation. An LLC designator is optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, so the description correctly spends its words elsewhere: it discloses the platform set, that some rows return 'manual check is needed' (a partial-result caveat), and that a full results URL is included. No latency, rate-limit, or auth context for a 23-platform open-world fan-out, which is the only notable gap.

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?

The core question is front-loaded, followed by scope, output shape, and the sibling alternative. The enumerated list of 23 platforms is long but earns its place by defining coverage precisely; the rest of the text is tight.

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 output schema, the description carries the return-value burden and does so: per-row status, the 'manual check needed' outcome, and a results URL. Input, output, coverage limits, and the sibling alternative are all present; only operational expectations (duration, partial failures) are unstated.

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?

One parameter with 100% schema coverage, so the schema already defines 'name' fully. The description adds only the framing that the handle is derived from the business name, which is a small but real clarification over the schema's field text.

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?

Specific verb plus resource ('check these social handles') with concrete scope: 23 named platforms, handle derived from a business name. It is clearly distinguishable from check_business_name, which is named as the broader alternative.

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?

Explicitly routes the agent: 'Use check_business_name instead for a complete name check,' and implies the use case is handle availability derived from a business name. It stops short of stating a when-not condition beyond the sibling comparison, but the alternative and its condition are stated.

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.

Resources