Skip to main content
Glama
istefox

istefox-dt-mcp

Official
by istefox

summarize_topic

Retrieves records related to a topic and groups them by date, tags, kind, or location to give you a structured overview of the subject.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesRetrieve records related to a topic and group them by dimension. Default dimensions are date and tags. The retrieval layer mirrors ``ask_database``: vector if RAG is enabled, BM25 fallback otherwise. When to use: - The user wants a panorama / overview of a topic across many records. - You need data already grouped by category (date, tag, kind, location) so you can narrate the structure without doing the grouping yourself. Don't use for: - Direct questions with a single answer -> use ``ask_database``. - Listing candidate documents to drill into -> use ``search``. Examples: - {"topic": "bollette 2025", "cluster_by": ["date", "tags"]} - {"topic": "Keraglass", "cluster_by": ["kind", "location"]}

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
successYes
audit_idNo
warningsNo
error_codeNo
error_messageNo
recovery_hintNo
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/istefox/istefox-dt-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server