Skip to main content
Glama

Jonas Splinter (jsplinter.nl)

List blog posts

list_posts
Read-onlyIdempotent

The longer blog articles on jsplinter.nl, newest first, each with date, summary, tags, reading time and URL. Optional: words to look for (any word may match) and a tag filter. Call get_post with a slug for the full text.

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

Input Schema

NameRequiredDescriptionDefault
tagNoOptional tag key as returned by list_tags, e.g. "mcp".
limitNoMaximum number of results (1-25, default 10).
queryNoOptional words to look for in title, summary and text, e.g. "mcp server". Max 120 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, non-open-world behavior, so the bar is lower; the description still adds real value by disclosing the result shape (date, summary, tags, reading time, URL), the newest-first ordering, and that query words match with OR semantics. It omits nothing critical, though it does not mention the 25-result ceiling or default page size, leaving that to the schema.

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?

Three tight sentences: identity and return shape first, optional filters second, sibling routing last. Every clause carries information an agent needs, with no filler.

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 correctly takes on the burden of describing return fields and ordering, and it adds the routing hint to get_post. Combined with full schema coverage and read-only annotations, an agent has everything needed to select and invoke it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by clarifying that any query word may match (OR semantics rather than requiring all words), which the schema text does not state. The tag filter is described in scope terms ('a tag filter'), though the identifier format is left to the schema's reference to list_tags.

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 resource ('The longer blog articles on jsplinter.nl'), its ordering ('newest first'), and its return fields, so the agent knows exactly what it gets. It also contrasts with the sibling get_post, which returns full text, so the tool is distinguishable without opening either schema.

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 selection guidance for the main fork: use this to browse post listings, and 'Call get_post with a slug for the full text.' It also notes the filters are optional, implying a no-arg call is valid. It does not address other listing siblings (list_updates, list_tags) explicitly, which keeps it short of a 5.

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