Skip to main content
Glama
Sign In

AgentBIT

by app.agentbit
OverviewDiscussionsAdmin

Academic Paper Search

agentbit.paper_search
Read-onlyIdempotent

Search academic literature across OpenAlex, Crossref and arXiv in one call: title, authors, year, venue, DOI, citation count, abstract and a DIRECT open-access PDF link where one exists. Deduplicated across sources, filterable by year and open-access, optional BibTeX per paper. One request replaces three APIs. Pay-per-call via x402 (USDC, Base).

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": {
      "query": "<query>"
    },
    "name": "agentbit.paper_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax papers to return (1-25, default 10)
queryYesSearch query: topic, title fragment, or author + topic (3-300 chars)
formatNo'bibtex' adds a ready-to-cite BibTeX entry per paper
_paymentNoOptional base64 x402 PAYMENT-SIGNATURE payload. Omit to receive payment requirements.
year_fromNoOnly papers published in or after this year
open_access_onlyNoOnly papers with a direct open-access PDF link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations declare read-only/idempotent/open-world, and the description adds value beyond them: dedup across sources, x402 pay-per-call in USDC on Base, and the omit-_payment-to-get-requirements flow. It doesn't mention rate limits or failure behavior, keeping it out of 5 territory.

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 dense sentence for capability plus one short sentence for payment, front-loaded with the core action. Every clause earns its place.

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?

Given a 6-param read tool with full schema coverage and no output schema, the description covers capability, sources, dedup, and the payment model. It stops short of describing result shape or pagination behavior, which is reasonable given the inline field list.

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 coverage is 100%, so the schema already documents all six parameters including enum and payment payload. The description restates year/open-access filters and per-paper BibTeX but adds little syntax or behavior not in the 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?

Specific verb+resource: 'Search academic literature across OpenAlex, Crossref and arXiv in one call' with an explicit return-field list. It distinguishes itself from sibling web_search/reddit_search by naming its scholarly sources and outputs.

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?

Implies usage when scholarly literature is needed, and names the three underlying APIs, but doesn't say when to prefer this versus web_search or other research siblings, or when not to use it.

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

All AgentBIT toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources