Skip to main content
Glama

get_paper_details

Retrieve detailed information about a specific cryptographic research paper using its unique ID from the IACR Cryptology ePrint Archive via a secure MCP server interface.

Instructions

Retrieve details of a specific paper by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paper_idYes

Implementation Reference

  • The handler function that implements the get_paper_details tool. It validates input with GetPaperDetailsSchema, fetches the IACR RSS feed, finds the paper by ID, extracts details, and returns them as JSON.
    private async getPaperDetails(args: unknown) {
      const validatedArgs = GetPaperDetailsSchema.parse(args);
      
      try {
        // Fetch RSS feed to get paper details
        const response = await axios.get(IACR_RSS_URL);
        const parsedFeed = await parseStringPromise(response.data);
        
        const paperItem = parsedFeed.rss.channel[0].item.find((item: any) => 
          item.link[0].split('/').pop() === validatedArgs.paper_id
        );
    
        if (!paperItem) {
          throw new Error('Paper not found');
        }
    
        const paperDetails = {
          id: validatedArgs.paper_id,
          title: paperItem.title[0],
          authors: paperItem['dc:creator'] ? paperItem['dc:creator'][0] : 'Unknown',
          abstract: paperItem.description[0],
          link: paperItem.link[0],
          date: paperItem.pubDate[0]
        };
    
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(paperDetails, null, 2)
          }]
        };
      } catch (error) {
        console.error('Paper Details Error:', error);
        throw new McpError(
          ErrorCode.InternalError,
          `Paper details retrieval failed: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • Zod schema defining the input for get_paper_details: requires a 'paper_id' string.
    const GetPaperDetailsSchema = z.object({
      paper_id: z.string()
    });
  • src/index.ts:81-91 (registration)
    Tool registration in the ListTools response, specifying name, description, and input schema matching the Zod schema.
    {
      name: 'get_paper_details',
      description: 'Retrieve details of a specific paper by its ID',
      inputSchema: {
        type: 'object',
        properties: {
          paper_id: { type: 'string' }
        },
        required: ['paper_id']
      }
    },
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 states the tool retrieves details but doesn't describe what those details include, whether it's a read-only operation, potential error conditions (e.g., invalid ID), or performance characteristics. This leaves significant gaps for an agent.

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 with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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?

For a tool with no annotations, no output schema, and low schema coverage, the description is inadequate. It doesn't explain what 'details' are returned, how errors are handled, or how this differs from sibling tools. More context is needed for effective use.

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 0%, so the schema provides no parameter documentation. The description adds value by explaining that 'paper_id' identifies a specific paper, but it doesn't specify the ID format, source, or constraints. This partially compensates but leaves the parameter underspecified.

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 ('retrieve') and resource ('details of a specific paper'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'search_papers' (which likely retrieves multiple papers based on criteria rather than a single paper by ID).

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 'search_papers' or 'download_paper'. It mentions retrieving by ID but doesn't clarify prerequisites (e.g., needing a paper ID from elsewhere) or exclusions (e.g., not for bulk retrieval).

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

Related 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/doomdagadiggiedahdah/iacr-mcp-server'

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