OSIRIS MCP

Official

Overview Schema Source Related Servers Discussions Admin

search_activities

Read-onlyIdempotent

Find research activities with citation-centered evidence. Filter by date, type, person, or unit to retrieve records with bibliometric references for informed decision-making.

Instructions

Search activities and return compact, citation-centered evidence.

Dates use YYYY-MM-DD and inclusively constrain the field selected by
``date_field``. Use ``start`` for activities that began in a period and
``end`` for activities completed in a period, such as completed theses.
By default, results include only affiliated activities and exclude records
marked Online ahead of print. Set the corresponding include flag to true
only when the user explicitly requests those exceptional records. Type,
subtype, person, unit, and topic filters require exact IDs obtained from
OSIRIS discovery tools. The server may search verbose source fields, but
never returns those raw fields. Optional bibliometric values include their
available reference or retrieval dates; do not treat a single metric as a
definitive measure of research quality. For exhaustive results, continue
with ``next_offset`` while ``has_more``.

Input Schema

TableJSON Schema

Name	Required	Default
`type`	No
`unit`	No
`limit`	No
`query`	No
`topic`	No
`offset`	No
`person`	No
`subtype`	No
`to_date`	No
`from_date`	No
`date_field`	No	start
`include_unaffiliated`	No
`include_online_ahead_of_print`	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.7/5.0

Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses substantial behavior: default filtering of unaffiliated and online-ahead-of-print records, the server's ability to search verbose source fields without returning them, the non-definitive nature of bibliometric values, and pagination behavior via next_offset and has_more. This goes well beyond structured metadata.

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 yet information-dense, front-loading the core purpose before addressing dates, defaults, filters, caveats, and pagination. Every sentence adds operational value, and there is no filler or repetition.

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?

For a 13-parameter search tool with no required parameters and an output schema, the description covers the critical ambiguities: date semantics, default exclusions, exact-ID requirements, server-side searching behavior, bibliometric caveats, and exhaustive pagination. An agent has enough context to invoke this tool correctly and interpret results.

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

Parameters4/5

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

With 0% schema description coverage, the description carries the full burden for parameter meaning. It explains date_field values, inclusive date constraints, filter IDs for type/subtype/person/unit/topic, and default/exceptional behavior of include flags. It does not explicitly describe query, limit, or offset, though pagination hints and schema defaults partially fill those gaps.

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 opens with a specific verb and resource combination: 'Search activities and return compact, citation-centered evidence.' This clearly identifies the operation and distinguishes it from sibling get_activity and search_people tools by emphasizing evidence-oriented search over a broad activity set.

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

Usage Guidelines4/5

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

The description gives explicit guidance on when to set include flags ('only when the user explicitly requests those exceptional records') and how to interpret date fields ('Use start for activities that began in a period'). It does not name alternatives for tool selection, but it gives enough contextual rules to use the tool correctly.

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

Deploy Server