Skip to main content
Glama
Sign In
kualat-mcp

kualat-mcp

by kualatLinks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List links

list_links
Read-only

Retrieve and page through account links, newest first by default, with search by URL, alias, or title and sorting by date or click count.

Instructions

Page through the links of the account, newest first by default.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
limitNoRows per page. Default 15.
orderNoSort by creation date or click count.
searchNoMatch the destination URL, alias or title.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds the useful default-ordering behavior ("newest first by default") but says nothing about return shape, total counts, or pagination termination — modest added value over the annotations.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity edges toward under-specification rather than maximally useful density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with four optional parameters and full schema coverage, the description covers the essentials (scope, pagination, default sort). It omits anything about result contents or how search interacts with listing, which an agent might reasonably want.

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 page, limit, order, and search are all documented in the schema itself. The description only reinforces the default ordering, which the order parameter already covers; no additional semantics are contributed.

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 gives a specific verb ("Page through") and resource ("the links of the account"), making clear this is a paginated list operation rather than a single-link fetch like get_link. It does not explicitly contrast itself with siblings, which keeps it at 4 rather than 5.

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?

"Page through the links of the account" implies the browsing/listing use case, and "newest first by default" hints at the default sort. There is no explicit when-not guidance, no mention of how this differs from get_link or a search-style tool, and no note on when to override the order parameter.

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