Skip to main content
Glama
whiteknightonhorse

APIbase

by whiteknightonhorse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Browse Figshare Subject Categories

figshare.taxonomy.categories
Read-onlyIdempotent

Browse or search Figshare’s subject taxonomy to classify research articles, filter categories by title, and retrieve category IDs, parent IDs, and taxonomy paths.

Instructions

Browse or search Figshare's subject taxonomy (2000+ categories, e.g. "Ecohydrology", "Agricultural biotechnology") used to classify research articles. Optionally filter by a free-text title query. Returns category id, title, parent_id, and taxonomy path — useful for understanding how Figshare organizes research by subject area. Data: Figshare.com, no auth required.

Input Schema

NameRequiredDescriptionDefault
limitNoMax categories to return (default 50, max 200).
queryNoOptional free-text filter on category/subject title (e.g. "ecology", "biotechnology"). Omit to browse the full taxonomy.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive behavior, so the description's job is lighter. It adds useful context: no auth required, data source, 2000+ categories, and the exact returned fields (id, title, parent_id, taxonomy path). It does not mention pagination or rate limits, which would have pushed it higher.

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?

Three efficient sentences front-load the core action and resource, then add optional filtering, return fields, and auth requirement. No filler; examples are embedded naturally.

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-only lookup with no required params, full schema coverage, and an output schema, the description supplies purpose, filter behavior, return fields, and auth status. Nothing an agent needs to decide whether to call it is missing.

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%; both parameters are already fully explained (limit default/max, query semantics with examples and browse behavior). The description only restates the query in general terms and does not add meaning beyond the schema, so baseline 3 applies.

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 names a specific verb ('Browse or search') and resource ('Figshare's subject taxonomy'), distinguishes it from article-level siblings by its subject-taxonomy focus, and grounds it with concrete examples. This is enough for an agent to know exactly what the tool offers.

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?

It clearly explains the two operational modes (browse all or filter by query) and the purpose ('used to classify research articles... how Figshare organizes research by subject area'). It does not explicitly name sibling alternatives or exclusion conditions, so it misses the top of the scale.

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