AMIRA — Africa Multiple Research Data

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

Resolve an entity

resolve_entity

Read-onlyIdempotent

Resolve a label or typed ID to cited candidates. Returns ambiguity instead of merging names. Use a returned id with get_entity_graph or get_* tools.

Input Schema

Name	Required	Description	Default
`type`	No
`limit`	No
`query`	Yes
`offset`	No

Output Schema

Name	Required	Description	Default
`hint`	No
`count`	Yes
`offset`	Yes
`results`	Yes
`has_more`	Yes
`ambiguous`	Yes
`next_offset`	No
`snapshot_id`	Yes
`suggestions`	No
`total_matches`	Yes
`effective_limit`	No
`requested_limit`	No
`response_limited`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026

addedOutput schema / properties / hint
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / suggestions

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "amira_url": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "amira_url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

AddedOct 7, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds real behavior context by stating it returns ambiguity instead of silently merging names. It stops short of describing pagination semantics or empty-result behavior, but the disambiguation policy is the important disclosure.

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 short sentences, front-loaded with the core action, then the key behavioral guarantee, then the follow-up tool. No filler and nothing redundant with the title.

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

Completeness4/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 explanation is not required, and annotations cover safety. The description supplies purpose, disambiguation policy, and next-step routing, which is nearly enough for a 4-param lookup tool; only the param semantics and alternative-tool routing are thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description must carry the burden. It only gestures at semantics via 'label or typed ID' (loosely mapping to query and type) and says nothing about limit or offset, leaving pagination behavior undocumented in both schema and description.

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 specific verb+resource ('Resolve a label or typed ID to cited candidates') and adds a distinguishing behavioral clause ('Returns ambiguity instead of merging names') that separates it from merge-style lookups. It does not explicitly contrast itself with the many search_* siblings, but an agent can still tell it resolves inputs to canonical IDs rather than searching for records.

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?

The description gives downstream guidance ('Use a returned id with get_entity_graph or get_* tools'), which is genuinely useful chaining advice. However it never states when to pick this over search / search_persons / get_person, nor what to do when resolution returns multiple candidates or none — usage is implied rather than explicit.

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.