Skip to main content
Glama

Florian Preisenhammer · AI Transformation Lead

Get an insight

get_insight
Read-onlyIdempotent

Get one Insight by slug: title, excerpt and themes in German and English, plus the page URL and a markdown_url with the full text.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_insight"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesInsight slug, from list_insights.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare read-only and idempotent behavior, so the description adds useful context beyond that by specifying the returned fields: bilingual title, excerpt, themes, page URL, and markdown_url with full text. It does not cover not-found or error behavior, but for a simple read operation it provides meaningful return semantics.

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?

The description is one sentence that front-loads the action and lookup key, then efficiently enumerates the returned content. There is no filler or redundant 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 one-parameter read tool with no output schema, the description gives enough detail about the return values to call it correctly. It omits not-found behavior and explicit slug-discovery guidance, which are minor gaps for this complexity level.

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?

The single slug parameter is already fully documented in the schema as coming from list_insights. The description repeats 'by slug' but adds no format examples, validation rules, or lookup nuances beyond what the schema provides.

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 a specific verb and resource ('Get one Insight') and the lookup key ('by slug'), which clearly distinguishes it from list_insights. It could more explicitly mention using list_insights to discover a slug, but the core purpose is clear.

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?

It implies the tool should be used when a slug is already known and describes the returned content. However, it does not explicitly state when not to use it or name list_insights as the discovery alternative; that hint appears only in the schema.

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