hrva.cc

Shorten a URL

shorten_url

Creates a new hrva.cc short link in the signed-in user's account. Each call makes a new link, so calling it again makes a second one; use list_links to find links that already exist. The destination gets the same safety checks as a link made on the hrva.cc website. Returns the full short URL and its destination, plus the visit limit and expiry when set. Every link created here gets the tag ai. A refused call creates nothing and returns the reason, for example "This destination is on a blocklist and can't be shortened. If you think that's a mistake, write to support@hrva.cc.", "Links to hrva.cc can't be shortened again. Use the final destination instead.", "This short URL is already taken. Try another." or "Custom short URL can only contain letters, numbers, hyphens and underscores". Once the visit limit is used up or the expiry has passed, the short link stops redirecting and visitors are told it is no longer available; the owner can turn it back on by editing it on hrva.cc.

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": {
      "url": "<url>"
    },
    "name": "shorten_url"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	The destination URL to shorten, for example https://example.com/page
`tags`	No	Tags for the link. The tag ai is always added, and a link keeps at most 10 tags of up to 30 characters each.
`alias`	No	Custom alias for the short link: letters, numbers, hyphens and underscores, up to 32 characters. A random alias is generated when omitted.
`expiresAt`	No	When the link stops working, as an ISO-8601 date-time with a time zone, for example 2026-12-31T23:59:00Z or 2026-12-31T23:59:00+01:00
`visitLimit`	No	Number of clicks after which the link stops working; every click counts, not counting bots

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=false, openWorldHint=true) by disclosing the automatic 'ai' tag, the destination safety checks, the exact failure modes and their messages, and what happens after the visit limit or expiry passes. Annotations already flag the write/non-idempotent profile, and the description adds real operational context on top.

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?

Front-loads purpose and the idempotency warning before the detail, which is the right order. It is somewhat long because it quotes four full error strings verbatim, and that list could be trimmed without losing actionable information.

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?

For a write tool with no output schema, it covers what is returned (full short URL, destination, visit limit, expiry), what the side effects are (ai tag, safety checks), and what failure looks like. Nothing an agent needs to call it correctly is missing.

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 baseline is 3, but the description adds meaning the schema doesn't: alias character rules appear as an error case, hrva.cc destinations can't be re-shortened, and alias collisions are refused. It does not restate expiresAt/visitLimit behavior beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Creates a new hrva.cc short link') plus its scope ('in the signed-in user's account'), and names the sibling to use for the opposite need, so an agent can distinguish it from list_links without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly warns that each call creates a new link and directs the agent to list_links when it instead wants an existing link, which is the exact when-to-use-this-vs-alternative guidance that matters here. It also implies the create-only nature that makes repeated calls non-idempotent.

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

All hrva.cc tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.