Skip to main content
Glama
Sign In
OpenAlex MCP Server

OpenAlex MCP Server

by SecretRichGarden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

openalex_cache_stats

Retrieve cache statistics or clear the cache to manage stored paper data, showing cached paper count, total size, and directory.

Instructions

Get cache statistics or clear the cache. Shows number of cached papers, total size, and cache directory.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "openalex_cache_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoAction: "stats" for statistics or "clear" to clear cachestats

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries full burden. It discloses that 'stats' shows cached papers count, size, and directory, but does not warn that 'clear' is destructive (data loss) or discuss permissions. Behavior for 'clear' is opaque.

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?

Two sentences, zero waste. Front-loads the primary purpose and then details output. Could be slightly more structured, but overall efficient.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple cache tool: describes both actions and output for stats. Lacks details on return format (e.g., JSON) and effect of clear. No output schema; description could be more complete.

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%. The description adds minimal value beyond the schema: it links the action parameter to the two operations. Baseline 3 is appropriate as the schema already defines the enum and default.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool shows cache statistics or clears the cache, using specific verbs ('Get', 'clear') and resource ('cache statistics'). However, it does not explicitly differentiate from sibling tools, though the unique function is evident.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, nor on whether to use 'stats' or 'clear'. The description lacks context about appropriate use cases or prerequisites.

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