Skip to main content
Glama

Florian Preisenhammer · AI Transformation Lead

List insights

list_insights
Read-onlyIdempotent

List published Insights by Florian Preisenhammer: case studies, essays and posts. Optionally filter by theme (case-insensitive substring).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 20, max 50).
themeNoOptional theme filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior: only published items are returned, and theme matching is case-insensitive substring rather than exact. It doesn't mention ordering or whether results are paginated beyond the limit param.

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 short sentences, front-loaded with purpose and followed by the filtering semantics. No redundant or filler wording.

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 simple two-parameter read tool with full schema coverage and read-only annotations, the description supplies the essentials: scope, published-only constraint, and filter semantics. Missing only result ordering/pagination behavior, which is minor and partly handled by the limit param.

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 baseline is 3, but the description goes beyond the schema's bare 'Optional theme filter' by specifying case-insensitive substring matching, which changes how an agent would form the value. The limit parameter is left entirely to the schema.

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?

States a specific verb and resource ('List published Insights') and characterizes the content types (case studies, essays, posts) plus the author. It does not explicitly contrast with the sibling get_insight, but the list-versus-single distinction is inferable from the wording and name.

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?

Implies usage by saying the theme filter is optional and describing it as a substring match, which tells the agent how to narrow results. However, there is no explicit statement of when to use this versus get_insight or the other list_* tools.

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