Skip to main content
Glama
nanyang12138

AI Research MCP Server

by nanyang12138

generate_daily_summary

Generate a daily summary of AI research activity by aggregating papers, GitHub repositories, and Hugging Face models to track research progress.

Instructions

Generate a comprehensive daily summary of AI research activity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_papersNoInclude papers section
include_reposNoInclude GitHub repos section
include_modelsNoInclude Hugging Face models section

Implementation Reference

  • Core handler function that implements the generate_daily_summary tool logic by fetching data from arXiv, HuggingFace, GitHub and formatting a markdown daily summary.
    async def _generate_daily_summary(
        self,
        include_papers: bool = True,
        include_repos: bool = True,
        include_models: bool = True,
    ) -> str:
        """Generate daily summary."""
        sections = []
        sections.append(f"# AI Research Daily Summary\n*Generated: {datetime.now().strftime('%Y-%m-%d %H:%M')}*\n")
        
        if include_papers:
            # Get papers from multiple sources
            hf_papers = await asyncio.to_thread(self.huggingface.get_daily_papers, days=1)
            arxiv_papers = await asyncio.to_thread(self.arxiv.get_latest_papers, days=1, max_results=20)
            
            all_papers = hf_papers + arxiv_papers
            sections.append(f"## 📄 Today's Featured Papers ({len(all_papers)})\n\n{self._format_papers(all_papers[:15])}")
        
        if include_repos:
            repos = await asyncio.to_thread(self.github.get_trending_repositories, period="daily")
            sections.append(f"## 🔥 Trending Repositories ({len(repos)})\n\n{self._format_repos(repos[:10])}")
        
        if include_models:
            models = await asyncio.to_thread(self.huggingface.get_llm_models, limit=15)
            sections.append(f"## 🤖 Popular Models ({len(models)})\n\n{self._format_models(models[:10])}")
        
        return "\n\n".join(sections)
  • Tool registration in list_tools() handler, including name, description, and input schema.
    Tool(
        name="generate_daily_summary",
        description="Generate a comprehensive daily summary of AI research activity",
        inputSchema={
            "type": "object",
            "properties": {
                "include_papers": {
                    "type": "boolean",
                    "description": "Include papers section",
                    "default": True,
                },
                "include_repos": {
                    "type": "boolean",
                    "description": "Include GitHub repos section",
                    "default": True,
                },
                "include_models": {
                    "type": "boolean",
                    "description": "Include Hugging Face models section",
                    "default": True,
                },
            },
        },
    ),
  • Input schema definition for the generate_daily_summary tool, specifying optional boolean flags for sections.
    inputSchema={
        "type": "object",
        "properties": {
            "include_papers": {
                "type": "boolean",
                "description": "Include papers section",
                "default": True,
            },
            "include_repos": {
                "type": "boolean",
                "description": "Include GitHub repos section",
                "default": True,
            },
            "include_models": {
                "type": "boolean",
                "description": "Include Hugging Face models section",
                "default": True,
            },
        },
    },
  • Dispatch logic in call_tool() handler that routes calls to the _generate_daily_summary method.
    elif name == "generate_daily_summary":
        result = await self._generate_daily_summary(**arguments)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'generate' and 'comprehensive', but doesn't disclose behavioral traits such as whether this is a read-only operation, if it requires authentication, rate limits, what format the summary is in, or how it sources data. This is inadequate for a tool with no annotation coverage.

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 a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part earns its place by specifying the action and scope concisely.

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?

Given no annotations, no output schema, and a tool that likely aggregates data from multiple sources, the description is incomplete. It doesn't explain what 'comprehensive' entails, how the summary is structured, or what the output looks like, leaving significant gaps for an AI agent to use it effectively.

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 description coverage is 100%, so the schema fully documents the three boolean parameters. The description adds no parameter-specific information beyond implying the summary includes papers, repos, and models, which aligns with the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 clearly states the verb 'generate' and resource 'comprehensive daily summary of AI research activity', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'generate_weekly_summary' or 'get_daily_papers', which would require mentioning time scope or comprehensiveness distinctions.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get_daily_papers', 'get_trending_models', and 'search_by_area', there's no indication of whether this tool aggregates those or serves a different purpose, leaving usage context unclear.

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/nanyang12138/AI-Research-MCP'

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