Skip to main content
Glama

Rybárstvo.sk

Blog articles

list_articles
Read-onlyIdempotent

Articles from the portal blog (portal news, how-tos and tips, waters, fish and nature, readers' stories): title, date, category, short excerpt and URL, newest first, optionally filtered by text or category. Content is in Slovak; reader articles are written by anglers.

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_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (default 8).
queryNoOptional search text.
categoryNoOptional category: novinky-portalu = portal news, navody-a-tipy = how-tos and tips, revire-a-vody = waters, ryby-a-priroda = fish and nature, pribehy-od-vody = readers' stories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and idempotency are covered structurally. The description adds useful context beyond that—result ordering, that content is in Slovak, and that reader articles are authored by anglers—but says nothing about pagination behavior or how the 20-item cap interacts with repeated calls, which is the main residual gap.

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?

Effectively one front-loaded sentence that leads with the resource and then packs fields, ordering, filtering, and locale. The parenthetical category list duplicates the enum descriptions already in the schema and is the one mildly wasteful element.

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?

With no output schema, the description compensates by naming the returned fields and their ordering, and it frames the domain and language for an agent unfamiliar with the portal. For a simple three-parameter, no-required-input list tool this is nearly complete; only pagination semantics are unaddressed.

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%, with limit, query, and category all documented in-schema including the full enum mapping. The description only restates that filtering is optional by text or category and adds no syntax, matching rules, or ranking behavior for the query parameter, 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+resource (articles from the portal blog) and enumerates the returned fields (title, date, category, excerpt, URL) plus ordering (newest first). This clearly separates it from siblings like list_catches, list_competitions, or search_site, which cover other content domains.

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

Usage Guidelines4/5

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

Gives clear usage context: optional filtering by free text or by category, and notes content is Slovak with reader-submitted angler stories, which informs when the tool is appropriate. It does not explicitly exclude alternatives or say when to prefer search_site over this, so it stops short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources