annas-mcp

Overview Schema Source Related Servers Discussions Admin

Provider allowance

account_status

Read-only

Check Anna's Archive membership and fast-download allowance, or OpenAlex API allowance by provider, to diagnose configuration and access issues.

Instructions

Inspect Anna's Archive membership and fast-download allowance, or OpenAlex API allowance with provider=openalex. Defaults to Anna when configured, otherwise OpenAlex. Use for configuration or allowance diagnosis. A status call is unnecessary before ordinary search or download.

Input Schema

Name	Required	Description	Default
`provider`	No	Optional provider: anna or openalex. Defaults to Anna when configured, otherwise OpenAlex. Reports allowance in the provider's own units; no status check is needed before downloading
`timeout_seconds`	No	Total operation timeout in seconds, including retries. Defaults to 60; maximum 86400

Output Schema

Name	Required	Description
`provider`	No	Provider that supplied this result
`next_args`	No	Arguments to replay for the next passage
`openalex_id`	No	Canonical OpenAlex W ID, usable by article_download
`details_args`	No	Arguments to article_details
`download_args`	No	Arguments to article_download for this selected work or copy
`next_search_args`	No	Provider-pinned article_search arguments for the next page

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv0.8.0Nov 4, 2026

addedInput schema / properties / provider

Added value: +{
+  "description": "Optional provider: anna or openalex. Defaults to Anna when configured, otherwise OpenAlex. Reports allowance in the provider's own units; no status check is needed before downloading",
+  "type": "string"
+}

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / details_args

Added value: +{
+  "additionalProperties": true,
+  "description": "Arguments to article_details",
+  "type": "object"
+}

addedOutput schema / properties / download_args

Added value: +{
+  "additionalProperties": true,
+  "description": "Arguments to article_download for this selected work or copy",
+  "type": "object"
+}

removedOutput schema / properties / downloads_left
```
Removed value: -{
-  "type": "integer"
-}
```
removedOutput schema / properties / downloads_limit
```
Removed value: -{
-  "type": "integer"
-}
```

removedOutput schema / properties / member

Removed value: -{
-  "type": "boolean"
-}

removedOutput schema / properties / memberships

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": [
-    "null",
-    "array"
-  ]
-}

addedOutput schema / properties / next_args

Added value: +{
+  "additionalProperties": true,
+  "description": "Arguments to replay for the next passage",
+  "type": "object"
+}

addedOutput schema / properties / next_search_args

Added value: +{
+  "additionalProperties": true,
+  "description": "Provider-pinned article_search arguments for the next page",
+  "type": "object"
+}

addedOutput schema / properties / openalex_id

Added value: +{
+  "description": "Canonical OpenAlex W ID, usable by article_download",
+  "type": "string"
+}

addedOutput schema / properties / provider

Added value: +{
+  "description": "Provider that supplied this result",
+  "type": "string"
+}

removedOutput schema / properties / window_hours
```
Removed value: -{
-  "type": "integer"
-}
```

removedOutput schema / required

Removed value: -[
-  "member",
-  "downloads_left"
-]

Addedv0.7.0Oct 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare read-only, non-destructive, open-world behavior, so the description's extra value is the defaulting rule (Anna when configured, otherwise OpenAlex) and the reassurance that no pre-check is required. It does not explain what the status response contains, but an output schema exists, so that is reasonable. The idempotentHint=false against a read-only status probe is slightly puzzling but not contradicted by the text.

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 tight sentences: what it inspects, the provider override, the default, then the usage rule. The most decision-relevant content (scope and the "no pre-check needed" guidance) is front-loaded with no filler.

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?

With only two optional parameters, an output schema present, and strong annotations, the description covers everything an agent needs to decide and call correctly. Nothing material is left to inference.

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%, so both parameters are already fully documented, including the provider default and timeout bounds. The description only restates the provider=openalex case and adds no syntax or unit detail 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?

States a specific verb ("Inspect") plus the exact resources: Anna's Archive membership/fast-download allowance and OpenAlex API allowance. It names the provider switch inline and is instantly distinguishable from the sibling search/download tools.

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

Usage Guidelines5/5

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

Explicitly scopes usage to "configuration or allowance diagnosis" and adds a clear negative rule: "A status call is unnecessary before ordinary search or download." It also explains the default provider resolution, so there is no ambiguity about when to call it or with what.

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

Deploy Server