Skip to main content
Glama

FoxAPIs data sources

Academic paper

academic_paper
Read-onlyIdempotent

A paper page (arXiv and similar): title, authors, abstract, date, DOI, journal and citation count where known, from its address. Costs 1 credit a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "academic_paper"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFor example: "https://arxiv.org/abs/1706.03762"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds genuinely new behavior: a 1-credit cost per call, no charge when no data is found, and an API-key requirement. It omits what an error or rate-limited response looks like, but the cost and auth disclosures are meaningful value beyond the structured fields.

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?

One sentence carries the resource, field list and input scoping, then a second compact sentence covers cost and auth. Nothing is padded and the most decision-relevant information (what you get, what it costs) is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the field enumeration is essential and present; cost, no-charge-on-empty and API-key needs round out the practical picture for a one-parameter lookup. Minor gaps remain around error states and whether the response is structured or prose, but the definition is adequate for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a worked example URL, so the baseline is already high. The description adds that the data returned is best-effort ("where known"), which tells the agent to expect partial records, and clarifies the URL is a paper address rather than a query string.

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?

States a specific resource (an academic paper page), names the concrete fields returned (title, authors, abstract, DOI, journal, citation count), and scopes the input to "its address," which separates it from search-style siblings like pubmed_search or biorxiv_preprints. It stops short of naming an alternative or exclusion, so a 4 rather than a 5.

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?

The phrase "from its address" implies you must already have the paper URL rather than a query, which is a useful usage signal. However, there is no explicit when-to-use vs. when-not, no mention of what to do when you only have a title or DOI instead of a URL, and no reference to the search-oriented siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources