Skip to main content
Glama

Figshare

by io.github.pipeworx-io

Articles

articles
Read-onlyIdempotent

AUTHORITATIVE search across figshare — the open-research repository hosting 7M+ papers, datasets, posters, code, theses, and supplementary materials from universities and labs worldwide. PREFER OVER WEB SEARCH for academic supplementary materials, dataset hunting, or research outputs that aren't in PubMed/arXiv (which skew biomed + physics). Returns article metadata + DOI, authors, license, download URL. Use for "find datasets about X", "supplementary materials for paper Y", "open-access PDFs of Z research".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
orderNopublished_date | modified_date | views | downloads | shares | cites
queryNo
item_typeNo1 figure | 3 dataset | 5 fileset | 12 thesis | etc.
page_sizeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoCurrent page number
itemsNoList of article search results
page_sizeNoResults per page

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "climate change datasets"
+  },
+  {
+    "item_type": 3,
+    "order": "downloads",
+    "page": 1,
+    "page_size": 20,
+    "query": "protein structure"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Search results for articles",
+  "properties": {
+    "items": {
+      "description": "List of article search results",
+      "items": {
+        "properties": {
+          "cites": {
+            "description": "Citation count",
+            "type": "number"
+          },
+          "description": {
+            "description": "Article description",
+            "type": "string"
+          },
+          "doi": {
+            "description": "Digital Object Identifier",
+            "type": "string"
+          },
+          "downloads": {
+            "description": "Download count",
+            "type": "number"
+          },
+          "handle": {
+            "description": "Figshare handle",
+            "type": "string"
+          },
+          "id": {
+            "description": "Article ID",
+            "type": "number"
+          },
+          "is_public": {
+            "description": "Public visibility",
+            "type": "boolean"
+          },
+          "modified_date": {
+            "description": "Last modified date",
+            "type": "string"
+          },
+          "published_date": {
+            "description": "Publication date",
+            "type": "string"
+          },
+          "shares": {
+            "description": "Share count",
+            "type": "number"
+          },
+          "title": {
+            "description": "Article title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Article URL",
+            "type": "string"
+          },
+          "views": {
+            "description": "View count",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "page": {
+      "description": "Current page number",
+      "type": "number"
+    },
+    "page_size": {
+      "description": "Results per page",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare read-only and idempotent behavior, so the description's main additions are repository scope and return metadata. It discloses that it returns DOI, authors, license, download URL, but doesn't cover pagination or sorting behavior beyond what schema provides. This adds some context without contradicting annotations.

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 four sentences, each providing distinct value: scope, preference guidance, return type, and example use cases. It is front-loaded with the primary purpose and uses emphasis for key guidance. Slightly longer than minimal but not verbose.

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 an output schema present and annotations covering safety, the description fills the main remaining gap of when to prefer this over alternatives. It could add detail on pagination or parameter interactions, but overall it's sufficient for effective selection. The examples and scope information make it contextually rich.

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

Parameters2/5

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

Schema description coverage is 40% (order and item_type have descriptions), but the tool description does not clarify query, page, page_size semantics. The use cases imply query usage but don't explain parameter formatting or constraints. Given low schema coverage, the description fails to compensate adequately.

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?

The description clearly identifies the tool as a search across figshare for academic research outputs, listing content types and return fields. It distinguishes from web search and PubMed/arXiv, demonstrating a specific verb+resource scope. While it doesn't explicitly contrast with sibling 'article', the search vs. detail distinction is clear.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states 'PREFER OVER WEB SEARCH' for specific use cases like finding datasets and supplementary materials, and provides concrete examples ('find datasets about X'). It also notes PubMed/arXiv limitations, giving clear when-to-use guidance. It doesn't mention sibling tools, but alternative positioning is strong.

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

All Figshare toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Multiple tools overlap heavily: ask_pipeworx and ask_pipeworx_beta are documented as currently identical, ask_pipeworx_grounded/deep_research route the same class of questions, and the six polymarket_* tools plus bet_research form a confusing cluster. Some clusters (Figshare fetch/search, memory, subscriptions) are distinct, but overall boundaries are frequently unclear.

Naming Consistency4/5

Names are uniformly lowercase snake_case and mostly follow a predictable verb_noun pattern (ask_pipeworx, list_subscriptions, resolve_entity, scan_dependency). The main inconsistency is the mix of bare-noun Figshare resource names (article, articles, collection, collections) with verb-phrase tool names.

Tool Count2/5

38 tools is well above the comfortable scope for a coherent server, especially one named Figshare. Most of the surface is unrelated to Figshare, bundling Pipeworx research, Polymarket analysis, memory, subscriptions, AI visibility, and npm checks into a single connection.

Completeness2/5

The Figshare read-side is reasonably covered (search, article metadata, files, collections, categories, licenses), but there are no create/update/delete or account/upload operations. The broader advertised surface is a grab bag with no clear domain boundary, and several subdomains are shallow while prediction markets are over-represented.

Resources