Skip to main content
Glama

Figshare

by io.github.pipeworx-io

Article

article
Read-onlyIdempotent

Fetch full metadata for a single Figshare article by numeric id, optionally at a specific version. Returns title, authors, description, DOI, license, categories, and file list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
versionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoArticle ID
doiNoDigital Object Identifier
urlNoArticle URL
tagsNoArticle tags
citesNoCitation count
titleNoArticle title
viewsNoView count
handleNoFigshare handle
sharesNoShare count
authorsNoList of authors
downloadsNoDownload count
is_publicNoPublic visibility
categoriesNoArticle categories
descriptionNoArticle description
modified_dateNoLast modified date
published_dateNoPublication date

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: +[
+  {
+    "id": 1234567
+  },
+  {
+    "id": 1234567,
+    "version": 2
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Single article details",
+  "properties": {
+    "authors": {
+      "description": "List of authors",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Author ID",
+            "type": "number"
+          },
+          "name": {
+            "description": "Author name",
+            "type": "string"
+          },
+          "orcid_id": {
+            "description": "ORCID identifier",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "categories": {
+      "description": "Article categories",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Category ID",
+            "type": "number"
+          },
+          "title": {
+            "description": "Category name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "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"
+    },
+    "tags": {
+      "description": "Article tags",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "description": "Article title",
+      "type": "string"
+    },
+    "url": {
+      "description": "Article URL",
+      "type": "string"
+    },
+    "views": {
+      "description": "View count",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds useful context about versioning and the specific fields returned, which goes beyond the structured annotations.

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?

Two sentences, front-loaded with the primary action and resource. No redundant wording, every phrase adds value.

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

Completeness5/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 rich annotations covering safety, the description provides all necessary context: purpose, parameter roles, and a summary of return fields. It is complete for a read-only fetch tool.

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 description coverage is 0%, so the description must explain parameters. It does so by identifying 'id' as a numeric identifier and 'version' as an optional specific version. This adds meaningful semantics beyond the raw schema, though it lacks constraints like range or default behavior.

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 states the tool fetches full metadata for a single Figshare article by numeric id, optionally at a specific version. This specific verb-resource pair distinguishes it from siblings like 'articles' (likely list) and 'article_files' (likely file list).

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

Usage Guidelines4/5

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

The description implies use for fetching a single article's metadata, contrasting with list tools, but does not explicitly name alternatives or state when not to use. The context is clear enough for an agent to decide, but lacks explicit exclusions.

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