Skip to main content
Glama

adamamer20-paper-search-mcp-openai

by ai.smithery
OverviewDiscussionsAdmin

search_crossref

Search academic papers from CrossRef database.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / kwargs
      Removed value: -{
-  "title": "kwargs",
-  "type": "string"
-}
    • removedInput schema / properties / max_results / title
      Removed value: -"Max Results"
    • changedInput schema / properties / max_results / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • changedInput schema / required
      Previous value: -[
-  "query",
-  "kwargs"
-]New value: +[
+  "query"
+]
    • removedInput schema / title
      Removed value: -"search_crossrefArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "search_crossrefOutput",
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Search' implies a read-only operation, the description omits critical details such as whether authentication is required, rate limits, what fields are searched (title, abstract, author?), and what the return structure contains (DOIs, metadata, abstracts?).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single six-word sentence with no redundancy. While appropriately sized for its content, the extreme brevity contributes to under-specification given the lack of schema documentation and annotations. It wastes no words but contains too few to be helpful.

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 rich ecosystem of sibling tools (16+ related search/read/download tools) and 0% schema coverage, the description is insufficient. It lacks guidance on the query interface, return format (critical for a search tool without output schema), and navigation of the CrossRef tool family. A user cannot determine what this returns versus what read_crossref_paper requires.

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

Parameters1/5

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

Schema description coverage is 0%, meaning neither 'query' nor 'max_results' have descriptions in the input schema. The description fails to compensate for this gap by providing no information about parameter semantics—such as expected query syntax (boolean operators supported?), or the valid range/behavior of max_results.

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 action ('Search') and resource ('academic papers from CrossRef database'), specifying the CrossRef source to differentiate from sibling search tools like search_arxiv. However, it fails to clarify the distinction between this tool and other CrossRef-specific siblings (read_crossref_paper, download_crossref, get_crossref_paper_by_doi).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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. It does not explain the difference between searching, reading, or downloading from CrossRef, nor when to prefer CrossRef over arxiv, pubmed, or other academic databases in the sibling list.

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

All adamamer20-paper-search-mcp-openai 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