openalex_mcp_classify_text – 1 MCP server offers this tool
What it usually takes
max_works– in 1 of 1text– in 1 of 1
No server marks it as only reading: treat it as able to change data.
From each publisher's own tool list. We never call a tool.
Servers
| Server | Inputs | Read-only? |
|---|---|---|
OpenAlex MCP Demo co.huggingface.geraldine/openalex-mcp Place a text in the OpenAlex topic hierarchy. OpenAlex retired its /text endpoint. This tool rebuilds the capability: one semantic search finds the nearest works, then their topics are aggregated weighted by relevance and rolled up to subfields, fields and domains. It returns real OpenAlex identifiers at all four levels plus the filter keys needed to reuse them — feed the ids straight back into search_works. Returns its own shape, not the record envelope: this tool returns no records. Calls run on the anonymous daily budget unless an X-Openalex-Api-Key request header is sent, or the deployment configured a key of its own. Returns: {"source": "openalex", "command": "classify_text", "query_used": str, "truncated": bool, "based_on_works": int, "topics": [{"id": str, "display_name": str, "score": float, "works": int}], "subfields": [object], "fields": [object], "domains": [object], "keywords": [str], "filter_keys": object, "cost_usd": float | null, "error": str | null} | max_works,text | Not stated |