Skip to main content
Glama
Sign In
research-hub

research-hub

by WenyuChiou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_topic_digest

Return all papers in a research cluster and produce a markdown digest to write an overview.

Instructions

Return every paper in a cluster plus a markdown digest for overview writing.

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": {
      "cluster_slug": "<cluster_slug>"
    },
    "name": "get_topic_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_slugYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the tool returns data and a digest, with no mention of side effects, permissions, or output format details. This is insufficient for full transparency.

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

Conciseness4/5

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

The description is a single sentence of 13 words, front-loaded with the action and result. It is concise but may be too brief, missing important details about the digest and parameter.

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

Completeness2/5

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

With no annotation support and a single undocumented parameter, the description fails to provide adequate context. The existence of an output schema partially compensates, but the input parameter and behavioral gaps remain.

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

Parameters2/5

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

The sole parameter 'cluster_slug' has no description in the schema (0% coverage). The tool description adds no explanation of what a cluster_slug is or how to obtain it, leaving the agent without required context.

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 clearly states the tool returns every paper in a cluster plus a markdown digest for overview writing. This distinguishes it from sibling tools like 'show_cluster' or 'summarize_cluster' by emphasizing the digest generation.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as 'show_cluster' or 'summarize_cluster'. The description does not provide context about prerequisites or use cases.

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

Deploy Server

Other Tools