Skip to main content
Glama
nanyang12138

AI Research MCP Server

by nanyang12138

generate_weekly_summary

Create a weekly summary of AI research activity by aggregating papers, GitHub repositories, and Hugging Face models to track progress across multiple sources.

Instructions

Generate a comprehensive weekly 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

  • The core handler function implementing the generate_weekly_summary tool logic: fetches weekly papers from multiple sources, trending repos, recent models, and formats into a markdown summary.
    async def _generate_weekly_summary(
        self,
        include_papers: bool = True,
        include_repos: bool = True,
        include_models: bool = True,
    ) -> str:
        """Generate weekly summary."""
        sections = []
        sections.append(f"# AI Research Weekly Summary\n*Generated: {datetime.now().strftime('%Y-%m-%d %H:%M')}*\n")
        
        if include_papers:
            hf_papers = await asyncio.to_thread(self.huggingface.get_daily_papers, days=7)
            arxiv_papers = await asyncio.to_thread(self.arxiv.get_latest_papers, days=7, max_results=50)
            pwc_papers = await asyncio.to_thread(self.papers_with_code.get_latest_papers, days=7)
            
            all_papers = hf_papers + arxiv_papers + pwc_papers
            sections.append(f"## 📄 This Week's Papers ({len(all_papers)})\n\n{self._format_papers(all_papers[:30])}")
        
        if include_repos:
            repos = await asyncio.to_thread(self.github.get_trending_repositories, period="weekly", max_results=30)
            sections.append(f"## 🔥 Trending Repositories ({len(repos)})\n\n{self._format_repos(repos[:20])}")
        
        if include_models:
            models = await asyncio.to_thread(self.huggingface.get_recent_models, days=7, limit=25)
            sections.append(f"## 🤖 New & Updated Models ({len(models)})\n\n{self._format_models(models[:15])}")
        
        return "\n\n".join(sections)
  • Tool registration in list_tools() handler, defining the tool name, description, and input schema.
    Tool(
        name="generate_weekly_summary",
        description="Generate a comprehensive weekly 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 defining optional boolean parameters for including papers, repos, and models in the summary.
        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 the main call_tool handler that invokes the weekly summary generator.
    elif name == "generate_weekly_summary":
        result = await self._generate_weekly_summary(**arguments)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'comprehensive' but doesn't specify what that entails, such as data sources, format, length, or processing time. It fails to address potential limitations like rate limits, authentication needs, or whether the operation is read-only or has side effects.

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 directly states the tool's purpose without any unnecessary words or fluff. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 the complexity of generating a summary from multiple sources (papers, repos, models) and the lack of annotations and output schema, the description is insufficient. It doesn't explain what the summary includes, its format, or how it's generated, leaving significant gaps for an AI agent to understand the tool's behavior and output.

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 input schema has 100% description coverage, so the schema already documents all parameters (include_papers, include_repos, include_models) with clear descriptions. The tool description adds no additional parameter information beyond what's in the schema, which is acceptable but not additive, resulting in the baseline score.

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 'weekly summary of AI research activity', making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from its sibling 'generate_daily_summary' beyond the temporal difference, which is why it doesn't reach a perfect score.

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 like 'generate_daily_summary' or other search tools. It lacks context about prerequisites, timing, or scenarios where a weekly summary is preferred over daily or other methods.

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