Skip to main content
Glama
Sign In

hrva.cc

by cc.hrva
OverviewDiscussionsAdmin

Link stats

link_stats
Read-onlyIdempotent

Shows click statistics for one of the signed-in user's own hrva.cc short links over the last 7, 30, 90 or 365 days (30 by default): clicks, daily unique visitors, bot clicks, top referrers, countries and devices, all-time visits, last visit and creation time (times in UTC). When the short link isn't known, call list_links first. It only works for the user's own links; for any other link it answers No link hrva.cc/ in your account.

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": {
      "link": "<link>"
    },
    "name": "link_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to cover: 7, 30, 90 or 365 (30 by default)
linkYesThe short link as menu, hrva.cc/menu or https://hrva.cc/menu, or as go.example.com/menu for a link on one of your own domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe read (readOnlyHint, idempotentHint, non-destructive), and the description adds genuine context beyond them: the returned metric set, UTC time zone for timestamps, the 30-day default, and the precise error string for links not in the account. That failure-mode disclosure is unusually useful for an agent deciding whether to call it.

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-loaded with the purpose and time windows; the sibling-routing note and error behavior come after. The long parenthetical inventory of returned metrics is dense but each item earns its place given there is no output schema.

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?

With no output schema, the description compensates by enumerating the returned data (clicks, unique visitors, bots, referrers, countries, devices, all-time visits, timestamps) and the time zone. Scope, default, and failure behavior are all covered for a two-parameter read tool.

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 the 7/30/90/365 enumeration and the 30-day default. The description restates the default and accepted windows without adding format or syntactic detail beyond the schema, so the baseline 3 applies.

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 ('Shows click statistics for one of the signed-in user's own hrva.cc short links') with the exact time windows supported. The scope restriction to the user's own links separates it cleanly from check_url and moderation siblings.

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 routes the agent: 'When the short link isn't known, call list_links first', naming the alternative and the condition that selects it. It also states the exclusion ('only works for the user's own links') and quotes the exact failure message for out-of-scope links.

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

All hrva.cc toolsInspect
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.

Resources