好縮 Short

Check Code Availability

check_code_availability

Read-onlyIdempotent

Check whether a custom short code (minimum 5 characters) is available and not a reserved system keyword.

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

Input Schema

Name	Required	Description	Default
`code`	Yes	Custom short code to check (e.g., vip2026)

Output Schema

Name	Required	Description
`code`	Yes	Checked code
`reason`	No	Explanation if unavailable
`available`	Yes	Whether the code is available

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation, so the description does not need to repeat that safety profile. The description adds useful behavioral constraints beyond the annotations: the minimum length requirement and the reserved-keyword exclusion.

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?

The definition is a single tightly written sentence with no wasted wording. The core purpose and key constraints are front-loaded.

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?

For a simple one-parameter read-only check with an output schema and full schema coverage, the description is nearly complete. A stronger definition would add that a successful check is not a reservation and would route agents to create_short_url when they are ready to create.

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

Parameters4/5

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

Schema coverage is 100%, so the single parameter is already documented in the schema. The description still adds meaning beyond the schema example by specifying the minimum 5-character rule and the reserved system keyword restriction.

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 states a specific verb and resource: checking whether a custom short code is available. It adds concrete validation rules (minimum 5 characters, not a reserved system keyword), but it does not explicitly distinguish itself from the sibling create_short_url workflow.

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 description implies usage as a pre-validation step before creating a short code, but it never says so explicitly. It also does not mention the alternative create_short_url or warn that a successful check does not reserve the code.

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

All 好縮 Short tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?