Skip to main content
Glama

Latest research

list_blog_articles
Read-onlyIdempotent

Latest published CheaterBusting research articles with canonical URLs and summaries, newest first.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum articles (1-50, default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare this as read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral context beyond that: it returns only published articles, returns them newest first, and includes canonical URLs and summaries.

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?

The definition is a single, front-loaded sentence with little wasted wording. There is minor redundancy between 'Latest' and 'newest first', but the overall size and structure are efficient.

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?

This is a low-complexity tool with one optional parameter, rich annotations, and no output schema. The description covers the resource, publication status, ordering, and returned content well enough for an agent to call it correctly, with minor gaps only around output shape details.

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%, and the single limit parameter is fully documented in the schema. The description does not add any parameter-specific meaning beyond what the schema already supplies, so the baseline score of 3 is appropriate.

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 states the specific resource retrieved: latest published CheaterBusting research articles. It adds scope details like canonical URLs, summaries, and newest-first ordering, though it does not explicitly differentiate itself from siblings such as search_site.

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 word 'Latest' implies the tool is for recent-article retrieval, and 'newest first' reinforces that ordering. However, there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives like search_site for keyword-based discovery.

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.