collectionsSearch Figshare collections (curated groups of articles) by keyword query; supports pagination via page/page_size. Returns collection id, title, description, and article count.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| query | No | ||
| page_size | No |
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Current page number | |
| items | No | List of collection search results | |
| page_size | No | Results per page |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "query": "machine learning"
+ },
+ {
+ "page": 2,
+ "page_size": 25,
+ "query": "genomics"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "description": "Search results for collections",
+ "properties": {
+ "items": {
+ "description": "List of collection search results",
+ "items": {
+ "properties": {
+ "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"
+ },
+ "type": "array"
+ },
+ "page": {
+ "description": "Current page number",
+ "type": "number"
+ },
+ "page_size": {
+ "description": "Results per page",
+ "type": "number"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds useful behavior: supports pagination and specifies return fields. No contradictions exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences front-load the main action and add pagination and return info. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has strong annotations, an output schema, and simple params. The description covers core purpose and pagination, but does not explain behavior when no query is provided (since all params are optional). Overall adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It does assign meaning to query ('keyword query') and page/page_size ('pagination'), but lacks detail on types, defaults, or constraints.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches Figshare collections by keyword, using a specific verb and resource. It does not explicitly distinguish from the sibling 'collection' tool, which likely fetches a single collection.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for keyword searches across collections, but it does not explicitly state when to use this tool over alternatives like 'collection' or provide exclusions. Usage context is present but not fully articulated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.