Skip to main content
Glama

Renameproof

Check one name in depth

check_name
Read-only

Check one name in depth: 7 domain endings (.com, .app, .io, .ai, .co, .dev, .net) and who uses each taken one, the App Store in the US, UK, India and Germany, Google Play, common iOS bundle IDs and Android package names, GitHub and npm. Returns a link to the full Renameproof report, which adds look-alike domains and a same-field verdict. Takes about 20 to 40 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": {
      "name": "<name>"
    },
    "name": "check_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe name to check, e.g. "pawtrail".
descriptionNoOptional: what the product is for, e.g. "a dog walking app". Passed to the full report link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description still adds real value: a 20–40 second latency expectation, the exact surface area probed, and the fact that the output is only a link to a fuller report. Disclosing that look-alike domains and the same-field verdict live outside this tool is exactly the kind of scope boundary an agent needs.

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?

Opens with the verb and payload, then lists coverage, then the return value and runtime. The enumeration of domain endings is long but each item is load-bearing scope information; the wording is dense without filler.

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 burden of explaining returns, and it does so ('a link to the full Renameproof report'), plus latency and coverage. It stops short of saying what the report contains per taken domain or how the response is structured beyond the URL, which is a minor residual gap.

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 description coverage is 100%, so both parameters are already documented, including that 'description' feeds the full report link. The description adds a concrete example context ('a dog walking app' is in the schema, not the description) but nothing structurally new, so baseline 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?

Names a specific verb and object (check one name) and enumerates the exact scope: 7 TLDs, App Store in four countries, Google Play, bundle IDs/package names, GitHub and npm. The phrase 'one name in depth' implicitly contrasts with the bulk sibling screen_names, but the sibling is never named, so the distinction relies on inference.

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?

Usage is implied by 'one name in depth' and by the note that the full report adds look-alike domains and a same-field verdict, which hints at when the lighter tool suffices. There is no explicit when-to-use/when-not statement and no routing to screen_names for multiple names.

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