Skip to main content
Glama

Figshare

by io.github.pipeworx-io

Collection

collection
Read-onlyIdempotent

Fetch full metadata for a single Figshare collection by numeric id, including title, description, authors, DOI, and list of contained article ids.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoCollection ID
doiNoDigital Object Identifier
urlNoCollection URL
titleNoCollection title
handleNoFigshare handle
articlesNoArticles in collection
descriptionNoCollection description
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": 9876543
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Single collection details",
+  "properties": {
+    "articles": {
+      "description": "Articles in collection",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Article ID",
+            "type": "number"
+          },
+          "title": {
+            "description": "Article title",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "description": {
+      "description": "Collection description",
+      "type": "string"
+    },
+    "doi": {
+      "description": "Digital Object Identifier",
+      "type": "string"
+    },
+    "handle": {
+      "description": "Figshare handle",
+      "type": "string"
+    },
+    "id": {
+      "description": "Collection ID",
+      "type": "number"
+    },
+    "published_date": {
+      "description": "Publication date",
+      "type": "string"
+    },
+    "title": {
+      "description": "Collection title",
+      "type": "string"
+    },
+    "url": {
+      "description": "Collection URL",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare the operation as read-only, idempotent, and non-destructive. The description adds the specific return fields (title, description, authors, DOI, article ids) which is useful, but this content is likely covered by the output schema. It does not disclose additional behavioral aspects like authentication, rate limits, or error handling.

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?

The description is a single, well-structured sentence that front-loads the action and resource, and includes specific examples of the metadata returned. No words are wasted, and the description is immediately understandable.

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?

For a simple read operation with one parameter, an output schema, and strong annotations, the description is sufficiently complete. It provides the essential information an agent needs to select and invoke the tool, and nothing critical is missing.

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?

With 0% schema description coverage, the description compensates by stating 'numeric id' and 'Figshare collection', giving meaningful context to the single 'id' parameter. It does not provide further format details or examples beyond the schema's type and example, but it adequately clarifies the parameter's purpose.

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 action ('Fetch full metadata'), the resource ('a single Figshare collection'), and the identifier format ('numeric id'). It also lists what is included in the metadata, distinguishing it from sibling tools like 'collections' which likely list multiple collections.

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 phrase 'single Figshare collection by numeric id' gives clear context for when to use it (when one specific collection's metadata is needed), and the sibling name 'collections' implies the alternative for listing. However, it does not explicitly mention alternatives or exclusion criteria, which prevents a perfect score.

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