Skip to main content
Glama
Sign In
kualat-mcp

kualat-mcp

by kualatLinks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get a link

get_link
Read-only

Retrieve a shortened link with click statistics split by country, referrer, browser, and OS for campaign and audience analysis.

Instructions

Read one link with its click statistics, split by country, referrer, browser and OS.

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": {
      "id": "<id>"
    },
    "name": "get_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLink id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly/openWorld/non-destructive, so safety is covered; the description adds that the call returns click statistics broken down along four dimensions, which is meaningful disclosure given there is no output schema. It stops short of covering failure behavior (e.g. unknown or deleted id) or pagination of stats, so not a 5.

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?

One sentence, front-loaded with the verb and scope, then the return content. Every clause carries information; nothing is redundant with the name or schema.

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 single-parameter read tool with no output schema, stating what the response contains is the key missing piece and it is supplied here. Remaining gaps (error/not-found semantics, stats time window) are minor but real.

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?

Only one parameter, fully documented in the schema at 100% coverage ('Link id.', positive integer). The description adds no extra semantics such as id format, where to obtain it, or whether it accepts ids of deleted links; schema baseline of 3 applies.

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?

A specific verb ('Read') plus a precisely scoped resource ('one link'), and it names the payload the response carries (click statistics by country, referrer, browser, OS). That makes it clearly distinct from a bulk lister like list_links, though no sibling is named explicitly.

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?

Usage is implied by 'one link' – fetch a single record when you already have its id – but the description never states when to prefer this over listing or searching, nor any precondition such as the id needing to exist.

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

Deploy Server

Other Tools