AMIRA — Africa Multiple Research Data

by io.github.AM-Digital-Research-Environment

Publication facets

list_publication_facets

Read-onlyIdempotent

Ranked facets for the entire filtered bibliography before pagination. Uses the same selection rules as search_publications.

Input Schema

Name	Required	Description
`type`	No	Exact type; discover values with list_publication_facets
`facet`	Yes
`limit`	No	Default 25, max 100
`venue`	No	Journal/book title, partial
`author`	No	Author/editor name, either name order
`offset`	No
`keyword`	No	Title, abstracts, venue, subjects or full text; every word must match, quote a phrase
`subject`	No	Subject heading, partial
`year_to`	No
`language`	No	Language name or ISO code
`year_from`	No
`added_since`	No	Added to AMIRA on or after this ISO date
`has_fulltext`	No	Filter by extracted full-text availability

Output Schema

Name	Required	Description	Default
`count`	Yes
`facet`	Yes
`offset`	Yes
`filters`	No
`results`	Yes
`has_more`	Yes
`next_offset`	No
`total_matches`	Yes
`missing_values`	Yes
`effective_limit`	No
`requested_limit`	No
`response_limited`	No
`total_publications`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 7, 2026
- addedInput schema / properties / added_since
```
Added value: +{
+  "description": "Added to AMIRA on or after this ISO date",
+  "maxLength": 40,
+  "type": "string"
+}
```
- addedInput schema / properties / author / maxLength
```
Added value: +1000
```
- changedInput schema / properties / keyword / description
```
Previous value: -"Title, abstract, venue, subjects or full text; substring match"New value: +"Title, abstracts, venue, subjects or full text; every word must match, quote a phrase"
```
- addedInput schema / properties / keyword / maxLength
```
Added value: +1000
```
- addedInput schema / properties / language / maxLength
```
Added value: +1000
```
- addedInput schema / properties / subject / maxLength
```
Added value: +1000
```
- addedInput schema / properties / type / maxLength
```
Added value: +1000
```
- addedInput schema / properties / venue / maxLength
```
Added value: +1000
```
- addedOutput schema / properties / response_limited
```
Added value: +{
+  "type": "boolean"
+}
```
First observedOct 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so safety is covered. The description adds genuinely new behavior: facets are computed over the entire filtered bibliography, not the current page, and results are ranked. That is exactly the trait that distinguishes facet aggregation from paginated search.

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?

Two sentences, front-loaded with the core behavior and followed by the routing/parameter-equivalence note. No filler, no restatement of the tool name or title.

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?

An output schema exists, so return-value shape needn't be explained, and annotations cover the safety profile. However, for a 13-parameter aggregation tool the description is thin: it never clarifies the relationship to list_years/list_subjects, nor what a facet result contains (values plus counts), leaving a real risk of misrouting.

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 69% and the 13 parameters are largely self-documented (facet is an enum, limit/offset ranges are stated). The description contributes only the "same selection rules as search_publications" equivalence, which adds some meaning but no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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?

States a concrete verb+resource: returns ranked facets for the bibliography, scoped to the whole filtered set before pagination. That scope statement distinguishes it from paginated document retrieval like search_publications. It does not, however, distinguish it from siblings such as list_years or list_subjects, which plausibly return the same facet dimensions as flat lists.

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?

"Uses the same selection rules as search_publications" tells the agent the filter parameters behave identically, which is useful routing context. But it never says when to choose this tool over search_publications or over the overlapping list_years/list_subjects siblings, so the selection decision is left to inference.

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

All AMIRA — Africa Multiple Research Data 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.