Skip to main content
Glama

List blog posts

list_blog_posts
Read-onlyIdempotent

The newest blog articles and short videos on AI governance and ISO standards: slug, title, description, date, language, author, topic, tags, url. A post is returned in the requested language when written in it, else in its own.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: en, de or sr. Default en.en
takeNoHow many to return, at most 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description contributes one genuinely non-obvious behavior — the language fallback ('returned in the requested language when written in it, else in its own') — but says nothing about ordering guarantees beyond 'newest' or about what an empty result means.

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?

Two sentences, front-loaded with the resource and scope, then the field list, then the localization rule. The field enumeration is long but earns its place because there is no output schema; no filler sentences.

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, describing the returned fields is necessary and is done well; the lang fallback semantics are also covered. Minor gaps remain around result ordering and whether take silently truncates the corpus, but the definition is sufficient to call the tool correctly.

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 would be 3, but the description adds real meaning beyond the schema: it explains the fallback resolution rule for the lang enum, which the schema does not state. The take parameter is not addressed directly, though 'newest' implies result ordering.

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 names the resource concretely ('The newest blog articles and short videos on AI governance and ISO standards') and enumerates the returned fields, so an agent knows exactly what this returns. It lacks an explicit verb and never contrasts itself with get_blog_post (single-post retrieval), so sibling differentiation is only implied by the plural resource.

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?

Usage is only implied: 'the newest' signals this is for browsing recent content, and the field list signals a listing operation. There is no explicit 'use this when' statement, no exclusion, and no pointer to get_blog_post for fetching a single article.

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