orthologous_eventsOrthologous pathways/reactions in another species.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Source Reactome event id. | |
| species | Yes | Target species (e.g. "Mus musculus"). |
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | Number of items returned. | |
| items | Yes | Orthologous pathways or reactions in the target species |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "id": "R-HSA-68886",
+ "species": "Mus musculus"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "count": {
+ "description": "Number of items returned.",
+ "type": "integer"
+ },
+ "items": {
+ "description": "Orthologous pathways or reactions in the target species",
+ "items": {
+ "properties": {
+ "className": {
+ "description": "Type of event",
+ "type": "string"
+ },
+ "dbId": {
+ "description": "Internal database ID",
+ "type": "number"
+ },
+ "displayName": {
+ "description": "Event name",
+ "type": "string"
+ },
+ "schemaClass": {
+ "description": "Schema class",
+ "type": "string"
+ },
+ "species": {
+ "properties": {
+ "dbId": {
+ "type": "number"
+ },
+ "displayName": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "stableId": {
+ "description": "Stable identifier",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "items",
+ "count"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true and destructiveHint=false, covering safety. However, the description adds no behavioral traits beyond that, such as return behavior, ordering, or limitations. It simply states purpose, which is already evident from the name and schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise at five words, with no wasted language. It front-loads the core concept, though it may be too terse to serve as a strong standalone definition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With a rich schema (100% param coverage), output schema, and annotations, the description can be minimal. However, it lacks usage context, examples, or any differentiation from siblings, making it only minimally complete for safe invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema describes both parameters with 100% coverage ('Source Reactome event id' and 'Target species'). The description does not add extra semantic meaning beyond the schema, but the schema itself is sufficient, so a baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Orthologous pathways/reactions in another species' clearly indicates the resource (orthologous pathways) but lacks an explicit verb like 'get' or 'find'. It distinguishes from siblings like 'pathway' by mentioning 'in another species', but the noun-phrase construction leaves the action implied.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. The sibling list contains related tools like 'pathway' and 'pathways_for_entity', but the description gives no context for choosing this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.