Skip to main content
Glama

Renameproof

Screen name ideas

screen_names
Read-only

Quickly check up to 10 candidate app, product or startup names. For each name it reports whether the .com and .app domains are registered (and, for a taken .com, what business or page is on it), whether an app with that name is on the US App Store or Google Play, and whether the GitHub name and npm package are taken. Use it on every name before suggesting it. Takes about 5 to 30 seconds.

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

Input Schema

NameRequiredDescriptionDefault
namesYesCandidate names, e.g. ["pawtrail", "leashly"]. Spaces are removed; letters, numbers and hyphens only.

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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only, external-network nature is covered. The description adds genuinely useful runtime context the annotations cannot: a 5-30 second latency expectation and the 10-name batch ceiling. It does not explain failure modes (what happens on partial lookups or rate limiting), which for a 30-second open-world call would matter.

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?

Two sentences, front-loaded with the capability and followed by the exact evidence returned per name. The latency note is short and actionable. No filler.

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

Completeness5/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 burden of describing returns, and it does so concretely per data source, including the bonus detail that a taken .com reveals what business sits on it. For a single-parameter, read-only lookup tool, an agent has everything needed to call it and interpret results.

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?

Schema coverage is 100%, and the schema already carries the 10-item maximum, the example array, and the normalization rule (spaces removed; letters, numbers and hyphens only). The description's 'up to 10 candidate names' merely echoes maxItems. Baseline 3 is correct when the schema does the heavy lifting.

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?

States a specific verb and resource ('check up to 10 candidate app, product or startup names') and enumerates exactly what each check returns: .com/.app registration, App Store/Google Play presence, GitHub and npm availability. That is far more than a restatement of the name. It does not, however, contrast itself with the sibling check_name, so an agent cannot tell from the description alone which of the two to pick.

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?

Gives an explicit directive: 'Use it on every name before suggesting it,' which tells the agent this is a pre-suggestion gate rather than an ad-hoc lookup. There is no when-not guidance and no named alternative, so it stops short of full routing guidance.

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