check_short_codeFREE, no API key needed. Check whether a custom short code is still free before trying to claim it with shorten_url. Codes are lowercase letters, digits and hyphens, up to 10 characters.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | The custom code to test, e.g. "spring26". |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the burden. It adds useful operational context: the tool is FREE, requires no API key, and is a non-mutating availability check rather than a claim action. It does not describe the exact response when a code is unavailable, but the read-only nature is clear.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences with no filler. Operational context and usage come first, format constraints last, and every sentence contributes useful information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter tool with no output schema, the description covers purpose, usage timing, input constraints, and cost/auth. The main gap is the exact return signal when the code is not free, but this is minor for an availability-check tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and includes an example. The description adds value beyond the schema by specifying accepted characters and length: lowercase letters, digits, hyphens, up to 10 characters, which helps avoid invalid calls.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: 'Check whether a custom short code is still free'. It also refers to shorten_url as the follow-up action, distinguishing this preflight check from the claiming tool and other link-management siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly positions the tool as a precondition: use it 'before trying to claim it with shorten_url'. It does not enumerate when not to use it or compare against other siblings, but the intended workflow is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes with strong descriptions, but three tools (create_qr, shorten_url, get_link_qr) can all produce a QR code, which could cause misselection without careful reading. The public-versus-account split and singular-versus-bulk variants are otherwise well separated.
All tool names follow a consistent verb_noun pattern in snake_case: check_, create_, delete_, expand_, get_, list_, shorten_, update_. Composite names like get_link_analytics and shorten_urls_bulk extend the pattern predictably without mixing conventions.
With 12 tools, the server is well-scoped for a QR and short-link management API. It includes public query tools, full CRUD for links, bulk creation, QR retrieval, analytics, and account status, with no unnecessary duplication.
The core link lifecycle is covered: create, read, list, update, delete, plus QR generation, analytics, and account info. Minor gaps exist around non-link resources like link-in-bio pages or restaurant menus that are only referenced by list_links, and there is no API to edit QR artwork directly, but these are peripheral to the stated purpose.