Skip to main content
Glama
oksure

OpenAlex Research MCP Server

by oksure

analyze_geographic_distribution

Analyze the geographic distribution of research activity on any topic. Identify leading countries and institutions by scientific output, with options to filter by year, exact phrase, or search field.

Instructions

Analyze the geographical distribution of research activity for a topic or query. Shows which countries and institutions are most active.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query or topic to analyze. For exact phrase matching (e.g., 'privacy paradox' as a specific concept), set exact_phrase to true.
exact_phraseNoSet to true for exact phrase matching. Without this, search terms are matched independently. Use this when searching for a specific concept or multi-word term (e.g., 'privacy paradox', 'supply chain resilience').
search_fieldNoRestrict search to a specific field: 'title' (paper titles only), 'abstract' (abstracts only), or 'fulltext' (full text only). By default, searches across all fields. Cannot be combined with exact_phrase.
from_yearNoAnalyze from this year onwards
to_yearNoAnalyze up to this year
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. While it states the output (countries and institutions), it does not explain whether results are aggregated, limited by data source, or if there are restrictions on query scope. Key behavioral details like caching, pagination, or API limits are missing.

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, front-loaded with purpose. Efficient but could be slightly more concise by merging the second sentence. No wasted words.

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

Completeness2/5

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

No output schema exists, so the description should explain the return value structure (e.g., list of countries with counts). It only vaguely mentions 'shows which countries and institutions are most active'. With 5 parameters and no annotations, the description lacks completeness for an analysis tool.

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 each parameter having a clear description. The description adds no new parameter information beyond what the schema provides. A baseline of 3 is appropriate since the schema already does the heavy lifting.

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 tool's function ('analyze the geographical distribution of research activity') and specifies what it shows ('which countries and institutions are most active'). This effectively identifies the tool's purpose and distinguishes it from siblings like 'analyze_topic_trends'.

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

Usage Guidelines3/5

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

No explicit guidelines on when to use this tool vs. alternatives (e.g., 'analyze_topic_trends'). The description implies usage for geographical analysis but lacks context about when it is appropriate or not, and does not mention prerequisites or limitations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oksure/openalex-research-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server