Skip to main content
Glama

Check a link name

check_handle
Read-onlyIdempotent

Is onmap.me/@name free for a business to claim? Says why when it is not.

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

Input Schema

NameRequiredDescriptionDefault
handleYesThe name to check, for example "sunrise-bakery".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description does add one piece of behavioral information beyond them — that the response includes a reason when the name is unavailable — but says nothing about the response shape, the meaning of 'free' (never registered vs. expired vs. reserved), or rate limits.

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?

Two short sentences with no filler, and the availability question is front-loaded. The second sentence is telegraphic enough ('Says why when it is not') that its referent takes a beat to resolve, which keeps it just short of ideal.

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 one-parameter, read-only tool with full schema coverage this is close to adequate, and the note about a reason on failure hints at return content despite there being no output schema. Still missing is what constitutes an unavailable name and the format of the handle input, which matters for a tool whose whole job is a binary answer.

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 single parameter already carries an example ('sunrise-bakery'), so the schema does the work. The description adds no meaning about accepted characters, length limits, or whether the leading '@' should be included.

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 names a specific resource (onmap.me/@name) and a specific question (is it free for a business to claim), which is far more concrete than the title's vague 'Check a link name'. It does not, however, distinguish itself from the sibling check_site, which an agent may reasonably confuse with this handle-availability check.

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?

Use is only implied: the phrase 'free for a business to claim' suggests this is a pre-registration availability check. There is no explicit when-to-use, when-not-to-use, or named alternative among the siblings, so an agent must infer the routing.

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.