OSIRIS MCP

Official

Overview Schema Source Related Servers Discussions Admin

list_topics

Read-onlyIdempotent

Find research topic IDs by listing or searching topics. Retrieve exact IDs needed for project filtering, with pagination support.

Instructions

List or search research topics and return their exact IDs.

Call this before using the ``topic`` project filter unless an exact topic ID
was already returned by OSIRIS. The result explicitly reports when topics
are not available for this installation. For a complete list, call again
with ``next_offset`` until ``has_more`` is false.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already convey readOnly, idempotent, openWorld, and non-destructive behavior. The description adds value beyond those annotations by disclosing that the result explicitly reports whether topics are available for the installation and that pagination is required for completeness. No contradiction with annotations.

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?

The description is compact and front-loaded: the core action and outcome appear first, followed by routing guidance and pagination details. Every sentence contributes necessary operational context and there is no filler.

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?

For a simple read-only list/search tool with an output schema and strong annotations, the description covers the key operational aspects: topic ID purpose, installation availability, and pagination. The main gap is precise parameter semantics, but the tool is simple enough that an agent can still invoke it correctly.

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%, so the description needed to compensate for limit, query, and offset. It only implies search behavior via 'List or search' and references next_offset without clearly mapping it to the offset input parameter. The description does not explain how query filtering behaves or how limit interacts with pagination, leaving a significant semantics gap.

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 a specific verb-and-resource action ('List or search research topics') and the distinctive output ('return their exact IDs'). It is easily distinguished from sibling tools like list_units and search_projects, and there is no tautology or ambiguity.

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?

The description explicitly says to call this before using the topic project filter unless an exact topic ID was already returned by OSIRIS. It also explains how to paginate to get the complete list with next_offset and has_more, providing concrete guidance for when to use the tool and when it can be skipped.

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

Deploy Server