Skip to main content
Glama
Sign In

FeatureOS

by io.github.featureos
OverviewDiscussionsAdmin

List changelogs

list_changelogs
Read-only

List changelogs with optional status/locale/label filtering and pagination. To find a changelog by keyword or topic, use search_changelogs instead.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1).
sortNoTime order: 'latest_created_at', 'oldest_created_at', 'latest_updated_at', or 'oldest_updated_at'. Omit for the default order.
localeNoFilter by language code, e.g. 'en', 'es', 'fr', 'de', 'pt', 'ja', 'ru', 'ko', 'zh', 'zh-TW', 'pt-BR', 'it', 'nl', 'tr', 'id', 'vi', 'th', 'pl', 'sv', 'ms', 'tl', 'da', 'ar'.
statusNoFilter by publish status ('published', 'unpublished', or 'scheduled').
label_idsNoOnly changelogs with any of these labels. Changelog label (tag) IDs from list_changelog_labels, as a JSON array of integers, e.g. [1779, 1781].

Output Schema

NameRequiredDescriptionDefault
pageNo
has_moreNo
per_pageNo
changelogsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds little beyond that – it does not mention result limits, max page size, or ordering defaults beyond what the schema already states. Adequate but not enriching.

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?

Two sentences, front-loaded with the capability and followed immediately by the alternative routing. No redundant wording or restatement of the title.

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 an output schema present, full parameter documentation, and annotations covering safety and world scope, the description supplies everything an agent needs: what it lists, how to filter, and where to go for keyword search.

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 coverage is 100%, so every parameter including the label_ids cross-reference to list_changelog_labels is already documented in the schema. The description merely echoes the filter categories at a high level without adding syntax, defaults, or interaction rules. Baseline 3 is correct when the schema does the heavy lifting.

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 states a specific verb and resource ('List changelogs') and enumerates the supported filters (status/locale/label) plus pagination, making it clearly distinct from mutation siblings like create_changelog or update_changelog and from search_changelogs.

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?

It explicitly names the sibling alternative search_changelogs and the condition that selects it ('keyword or topic' lookup), which is exactly the routing an agent needs. It stops short of stating when to prefer get_changelog for a single known record, so it falls just under a 5.

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

All FeatureOS toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources