Skip to main content
Glama
Dianel555

Paper Search MCP

by Dianel555
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_webofscience

Search academic papers on Web of Science using Starter or Expanded API. Filter results by author, year, journal, and sort by relevance, date, or citations.

Instructions

Search Web of Science Starter (default) or explicitly selected Expanded API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoPublication year filter (e.g., "2023", "2020-2023")
queryYesSearch query string
authorNoAuthor name filter
sortByNoStarter-supported sort field
journalNoJournal name filter
sortOrderNoSort order: ascending or descending
apiProductNoAPI product; Expanded must be selected explicitlystarter
maxResultsNoMaximum number of results to return
recordViewNoExpanded record detail; defaults to short
discoverAccessNoFind public publisher PDF links using controlled direct retrieval and optional paid fallback
discoverAccessMaxItemsNoMaximum result items to enrich; defaults to ACCESS_DISCOVERY_MAX_ITEMS or 5

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.3.2
    • addedInput schema / properties / apiProduct
      Added value: +{
+  "default": "starter",
+  "description": "API product; Expanded must be selected explicitly",
+  "enum": [
+    "starter",
+    "expanded"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / discoverAccess
      Added value: +{
+  "default": false,
+  "description": "Find public publisher PDF links using controlled direct retrieval and optional paid fallback",
+  "type": "boolean"
+}
    • addedInput schema / properties / discoverAccessMaxItems
      Added value: +{
+  "description": "Maximum result items to enrich; defaults to ACCESS_DISCOVERY_MAX_ITEMS or 5",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "number"
+}
    • addedInput schema / properties / maxResults / default
      Added value: +10
    • changedInput schema / properties / maxResults / maximum
      Previous value: -50New value: +100
    • addedInput schema / properties / recordView
      Added value: +{
+  "description": "Expanded record detail; defaults to short",
+  "enum": [
+    "short",
+    "full"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / sortBy / description
      Previous value: -"Sort results by field"New value: +"Starter-supported sort field"
    • changedInput schema / properties / sortBy / enum
      Previous value: -[
-  "relevance",
-  "date",
-  "citations",
-  "title",
-  "author",
-  "journal"
-]New value: +[
+  "relevance",
+  "date",
+  "citations"
+]
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only mentions that Starter is the default and Expanded must be explicitly selected. It does not mention the return format, pagination behavior, rate limits, or side effects (e.g., discoverAccess fallback). The description carries a minimal behavioral disclosure, leaving most of the tool's behavior opaque.

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, concise sentence that front-loads the core action. It is not verbose and has no filler. However, it is so brief that it sacrifices valuable context, but that is more a completeness issue than a conciseness issue. For the length it has, it is well-structured.

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

Completeness1/5

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

Given the tool has 11 parameters, no annotations, and no output schema, the description is severely incomplete. It does not explain that this searches scholarly literature, what types of queries are supported, or how it compares to the many sibling search tools. An agent has almost no guidance on what to expect or how to call it correctly beyond the schema.

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 100%, so all parameters are documented in the schema. The description adds only that 'Starter (default) or explicitly selected Expanded API', which essentially repeats the schema's default and description for apiProduct. Thus, it adds minimal value beyond the schema, and the baseline of 3 is appropriate.

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 states a clear verb ('Search') and resource ('Web of Science'), and distinguishes between the two API products (Starter vs Expanded). It is specific enough to differentiate from siblings like search_google_scholar or search_pubmed, though it does not mention the nature of the content (scholarly database).

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?

No guidance is given on when to use this tool versus the many sibling search tools. It does not mention that this is for Web of Science specifically, nor does it provide exclusions or alternatives. The only hint is the name, which is insufficient for an agent to decide between search_webofscience and search_scopus or search_crossref.

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

Deploy Server

Other Tools