Eol

Pages By Name

pages_by_name

Read-onlyIdempotent

Find EOL page id(s) for an exact scientific name.

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": {
      "name": "Panthera leo"
    },
    "name": "pages_by_name"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	e.g. "Panthera leo"

Output Schema

Name	Required	Description	Default
`name`	Yes	The scientific name searched for
`matches`	Yes	EOL page results matching the exact name

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "name": "Panthera leo"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "matches": {
+      "description": "EOL page results matching the exact name",
+      "items": {},
+      "type": "array"
+    },
+    "name": {
+      "description": "The scientific name searched for",
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "matches"
+  ],
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive, covering behavioral safety. The description adds no further behavioral details (e.g., rate limits, authentication, or what happens on missing names). It does not contradict 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 (10 words) that communicates the core purpose efficiently. No extraneous information, and the key verb and resource are front-loaded.

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?

Given the tool's simplicity (1 required parameter, output schema present), the description adequately explains input and output. It could mention whether multiple IDs are possible or what happens if the name is not found, but this is minor given the output schema likely covers return format.

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% and the parameter description in the schema ('e.g. "Panthera leo"') is already clear. The tool description ('exact scientific name') adds no new semantic value beyond what the schema provides, meeting baseline expectations.

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 action ('Find'), a specific resource ('EOL page id(s)'), and a specific input condition ('exact scientific name'). This distinguishes it from sibling tools like get_page (which retrieves a page by ID) and search (which supports partial matches).

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 usage for exact scientific name lookups but does not explicitly state when to use this tool over alternatives (e.g., search, search_within) or when not to use it (e.g., for common names). No exclusions or prerequisites are mentioned.

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.