SiteCheck Web Intel

Figshare public article search: id, title, DOI, publication

search_figshare_articles

Read-only

Figshare public article search (public API, no key): id, title, DOI, publication date, item type and public page link for research articles, datasets and figures. Searches titles and metadata; file contents are not returned. Related tools on this server, for a different need: search_al_jazeera_articles when you need Al Jazeera latest articles from its public RSS feed; search_bbc_news_articles when you need BBC News top stories from the public BBC RSS feed. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "search_figshare_articles"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Search words (1 to 200 characters)
`limit`	No	How many articles, 1 to 25 (default 5)

Output Schema

Name	Required	Description	Default
`q`	No
`count`	No
`items`	No
`source`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real context on top: no API key required, the searchable surface is metadata only with no full text, and a per-call cost of $0.002 in USDC via x402 with failed calls not charged. Cost and authentication behavior are exactly what an agent needs before spending a call.

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 capability and return fields are front-loaded in the first sentence, with exclusions and routing following. The sibling-routing and pricing sentences are useful but somewhat boilerplate-heavy for a two-parameter tool; nothing is actively wasteful.

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?

An output schema exists, so the description need not explain return values, and the simple two-parameter surface is fully covered by the schema. The remaining shortfall is disambiguation against the many other academic-metadata search siblings, which the description never addresses.

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%, with both q and limit described in the schema including ranges and defaults, so the baseline of 3 applies. The description adds no query syntax, field-scoping, or matching-behavior detail beyond what the schema already states.

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?

States a specific verb and resource ('Figshare public article search') plus the exact scope (research articles, datasets, figures) and the fields returned. An agent can immediately tell this queries Figshare metadata rather than a news feed or a generic web search.

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?

Explicitly rules out one misuse case ('Searches titles and metadata; file contents are not returned') and names two sibling alternatives with the condition selecting each (Al Jazeera RSS, BBC RSS). The gap is that it does not differentiate from its closest academic siblings in the list, such as search_crossref_academic_paper, search_datacite_metadata, or search_pubmed_article_metadata, leaving the agent to guess among them.

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

All SiteCheck Web Intel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?