Flinty

Topic Clusters

list_clusters

Read-onlyIdempotent

List all topic clusters for this blog with their status and metrics. satellites_published/pillar_published only cover this cluster's own subjects — they don't include articles published outside the cluster pipeline (YouTube import, web import, Reddit, etc). For a tenant's true total published article count, use list_articles. Response is capped (default 50, max 200) — check has_more before assuming the list is complete.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Max clusters to return (1-200, default 50)

Output Schema

Name	Required	Description	Default
`clusters`	Yes
`has_more`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the scope limitation of satellites_published/pillar_published and the result cap (default 50, max 200) with a has_more check, which prevents the agent from misreading a truncated result.

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: purpose first, then the metric-scope caveat, then the pagination caveat. Every sentence carries information the agent needs and nothing is repeated.

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?

The tool is simple (one optional param) and an output schema already covers return values, so the description only needs to cover interpretation pitfalls and pagination — both of which it does. Nothing required to call it correctly is missing.

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% for the single limit parameter, whose range and default are already documented in the schema. The description restates the default/max rather than adding new meaning, so the baseline 3 applies.

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 verb and resource ('List all topic clusters for this blog') plus the payload ('status and metrics'), which cleanly separates it from get_cluster (single) and create_cluster (mutation) among the siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative for a related question ('For a tenant's true total published article count, use list_articles') and warns that the cluster's published counters do not include out-of-pipeline articles. It also tells the agent to verify completeness via has_more before treating the list as exhaustive.

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

All Flinty tools Inspect

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

Need Help?