Skip to main content
Glama

get_citeas_data

Retrieve BibTeX-formatted citations for resources like DOIs, URLs, or keywords directly from CiteAs. Simplify your research workflow by automating citation retrieval.

Instructions

Retrieve BibTeX-formatted citation for the specified resource (e.g., DOI, URL, keyword) from the CiteAs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resourceYes

Implementation Reference

  • The handler function for the 'get_citeas_data' tool. It is decorated with @mcp.tool() which registers it with the MCP server. Fetches BibTeX citation data from the CiteAs API for a given resource (e.g., DOI). Includes inline schema via type hints and docstring.
    @mcp.tool()
    def get_citeas_data(resource: str) -> str:
        """Retrieve BibTeX-formatted citation for the specified `resource` (e.g., DOI, URL, keyword) from the CiteAs"""
        response = httpx.get(f"https://api.citeas.org/product/{resource}?email=default@example.com")
        response.raise_for_status()
        data = response.json()
        return next((export["export"] for export in data["exports"] if export["export_name"] == "bibtex"), None)
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 data, implying a read-only operation, but doesn't cover important aspects like error handling, rate limits, authentication needs, or response format details beyond 'BibTeX-formatted'.

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, efficient sentence that clearly states the tool's purpose and parameter usage. It's appropriately sized for a simple tool with one parameter, though it could be slightly more structured with separate usage guidance.

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 lack of annotations and output schema, the description is incomplete for a tool that presumably returns structured citation data. It doesn't explain what happens with invalid inputs, the format of returned BibTeX, or how this differs from the sibling tool's functionality.

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 description adds meaningful context by explaining that the 'resource' parameter can be a DOI, URL, or keyword, which goes beyond the schema's generic 'string' type. However, with 0% schema description coverage and only one parameter, this provides adequate but not comprehensive semantic information.

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 the resource 'BibTeX-formatted citation', specifying it's from the CiteAs service. It distinguishes from the sibling tool 'get_scholar_data' by focusing on citation formatting rather than scholarly data, though the distinction could be more explicit.

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 minimal guidance by mentioning the resource parameter can be a DOI, URL, or keyword, but offers no explicit advice on when to use this tool versus the sibling 'get_scholar_data'. It lacks context on 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

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/ndchikin/reference-mcp'

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