Eol

Get Page

get_page

Read-onlyIdempotent

Fetch a taxon page by EOL id (synonyms, common names, hierarchy summary).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": 328672
    },
    "name": "get_page"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	EOL page id (from /search)
`detail`	No	Include data objects (texts, images). Default false.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "id": 328672
+  },
+  {
+    "detail": true,
+    "id": 328672
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Taxon page with synonyms, common names, hierarchy summary, and optional data objects",
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and open-world. The description adds value by specifying the returned content (synonyms, common names, hierarchy summary), enhancing transparency beyond 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 a single, concise sentence with only 12 words. It efficiently conveys the tool's purpose without unnecessary information.

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 tool with two parameters and an output schema, the description is complete. It covers what the tool does and what it returns. No additional context seems necessary.

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 coverage is 100%, so the description does not add new parameter information. It merely echoes the schema by mentioning 'EOL id', but the schema already provides detailed descriptions for both parameters.

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 the tool fetches a taxon page by EOL id, with specific content (synonyms, common names, hierarchy summary). This precise verb-resource-object combination distinguishes it from sibling tools like pages_by_name or search.

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 implies use when an EOL id is available but does not explicitly state when to use this tool versus alternatives like pages_by_name or search. No exclusion criteria or prerequisites are provided.

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

All Eol 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.