Skip to main content
Glama
AI-Archive-io

AI-Archive MCP Server

get_citation_stats

Retrieve detailed citation statistics for a research paper, including citation count and trends.

Instructions

Get detailed citation statistics for a paper

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paperIdYesID of paper to get citation stats for

Implementation Reference

  • The main handler function for the 'get_citation_stats' tool. It extracts the paperId from args, calls the API endpoint /citations/{paperId}/stats, and formats the response with detailed citation statistics including counts, impact metrics, temporal analysis, and field comparison.
    async getCitationStats(args) {
      const { paperId } = args;
      
      try {
        const response = await this.baseUtils.makeApiRequest(`/citations/${paperId}/stats`, 'GET', null, false);
        const stats = response.data;
        
        return this.baseUtils.formatResponse(
          `📊 **Citation Statistics for Paper ${paperId}**\n\n` +
          `**Citation Counts:**\n` +
          `• Total Citations: ${stats.totalCitations || 0}\n` +
          `• Direct Citations: ${stats.directCitations || 0}\n` +
          `• Self Citations: ${stats.selfCitations || 0}\n` +
          `• References Made: ${stats.referencesCount || 0}\n\n` +
          `**Impact Metrics:**\n` +
          `• H-Index Contribution: ${stats.hIndexContribution || 0}\n` +
          `• Citation Velocity: ${stats.citationVelocity || 0} citations/month\n` +
          `• Peak Citation Year: ${stats.peakYear || 'N/A'}\n\n` +
          `**Temporal Analysis:**\n` +
          `• First Citation: ${stats.firstCitation ? new Date(stats.firstCitation).toLocaleDateString() : 'None'}\n` +
          `• Latest Citation: ${stats.latestCitation ? new Date(stats.latestCitation).toLocaleDateString() : 'None'}\n` +
          `• Citation Half-Life: ${stats.halfLife || 'N/A'} months\n\n` +
          `**Comparison:**\n` +
          `• Percentile in Field: ${stats.fieldPercentile || 'N/A'}%\n` +
          `• Above Average: ${stats.aboveAverage ? 'Yes' : 'No'}`
        );
      } catch (error) {
        if (error.response?.status === 404) {
          throw new McpError(ErrorCode.InvalidRequest, `Paper ${paperId} not found`);
        }
        throw new McpError(ErrorCode.InternalError, `Failed to get citation stats: ${error.message}`);
      }
    }
  • The input schema definition for the 'get_citation_stats' tool, registered in getToolDefinitions(). Defines a single required parameter 'paperId' (string) for identifying the paper to get stats for.
    {
      name: "get_citation_stats",
      description: "Get detailed citation statistics for a paper",
      inputSchema: {
        type: "object",
        properties: {
          paperId: { type: "string", description: "ID of paper to get citation stats for" }
        },
        required: ["paperId"]
      }
    }
  • Registration of the 'get_citation_stats' tool handler in getToolHandlers(), mapping the tool name to the getCitationStats method bound to the instance.
    getToolHandlers() {
      return {
        "get_citations": this.getCitations.bind(this),
        "get_citing_papers": this.getCitingPapers.bind(this),
        "get_paper_references": this.getPaperReferences.bind(this),
        "get_citation_graph": this.getCitationGraph.bind(this),
        "get_citation_stats": this.getCitationStats.bind(this)
      };
Behavior2/5

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

No annotations provided; description lacks details on what 'detailed' means, return format, or side effects. Minimal disclosure beyond the basic action.

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?

Single sentence with no waste; concise but could include slightly more context without becoming verbose.

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?

No output schema; description does not specify what citation statistics are returned or any additional context needed for complete understanding.

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?

Only one parameter 'paperId' is fully described in the schema (100% coverage); description adds no extra meaning beyond schema.

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 specifies the verb 'get' and resource 'citation statistics' for a paper, distinguishing it from sibling tools like 'get_citation_graph'.

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?

No explicit guidance on when to use or avoid, but the name and description imply usage for retrieving citation statistics; absence of alternatives or exclusions.

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/AI-Archive-io/MCP-server'

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