Skip to main content
Glama
Sign In
linkwarden-mcp

linkwarden-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get the dashboard links

get_dashboard
Read-only

Pulls the dashboard links from Linkwarden: recent additions merged with pinned items, deduplicated, for a quick overview.

Instructions

Returns the links Linkwarden shows on its dashboard: the most recently added ones together with everything the account has pinned, deduplicated. A quick "what is going on here" overview — use search_links for anything targeted.

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": "get_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.5/5.0
Behavior4/5

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

The annotation already declares readOnlyHint=true, so the tool is understood to be a safe read. The description adds value by explaining the specific content (recent + pinned, deduplicated) and framing it as a dashboard overview. However, it doesn't detail pagination behavior or limits on the returned set, which would be helpful but is a minor gap given the tool's simplicity.

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?

The description is two sentences with zero filler. The first sentence states the core functionality, and the second provides usage context. Every word serves a purpose, and it is perfectly front-loaded.

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?

Given the tool has no parameters, no output schema, but has complete annotations, the description covers everything: what the tool returns, its behavioral characteristics (deduplication, composition), and when to use an alternative. There are no gaps for the intended oversight use case.

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% because there are no parameters. The description doesn't need to add parameter info; it naturally explains what the tool returns. Baseline 3 is appropriate as the schema and description together are complete.

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?

The description clearly states the tool returns the links shown on the Linkwarden dashboard, specifically the most recently added ones together with pinned items, deduplicated. The verb 'returns' and resource 'the links Linkwarden shows on its dashboard' are specific and unambiguous, and the mention of deduplication adds precision that distinguishes it from a generic link listing.

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?

The description explicitly says this is for a 'quick overview' and directs the agent to use 'search_links for anything targeted.' This provides clear guidance on when to use this tool versus alternatives, making the sibling differentiation immediate and actionable.

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