Skip to main content
Glama
Sign In
lontar-mcp

lontar-mcp

by thesimonharms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_posts

Retrieve a paginated list of published blog posts with title, slug, excerpt, and publication date.

Instructions

List published blog posts (paginated). Returns title, slug, excerpt, and published_at for each post.

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
pageNoPage number (default: 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden. It states pagination and the returned fields but does not disclose ordering, rate limits, or that it is read-only. The behavior is adequately implied for a simple list tool.

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 a single, efficient sentence that front-loads the action ('List published blog posts') and result ('Returns...'). No wasted words.

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 low-complexity tool with one optional parameter and no output schema, the description is sufficiently complete. It could optionally mention ordering but is not deficient.

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?

The only parameter, page, is already fully described in the input schema (type, default, min, max). The description only mentions 'paginated', adding no extra semantic meaning beyond schema coverage.

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 lists published blog posts with pagination, and specifies the returned fields (title, slug, excerpt, published_at). This distinguishes it from sibling tools like list_drafts or get_post.

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?

The description implies use for retrieving published posts but does not explicitly state when to use this tool over alternatives like list_drafts or get_post. No prerequisites or exclusions are mentioned.

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