PhyloPic MCP Server

Search Images by Node

search_images_by_node

Find all silhouette images for a specific phylogenetic node by UUID. Use this to retrieve images of a particular taxon, such as Homo sapiens.

Instructions

List silhouette images that directly represent a specific phylogenetic node. Use this to find all images of a particular taxon (e.g. all images of Homo sapiens). For ancestral nodes, consider using 'search_images_by_clade' instead to get images of all descendant taxa as well.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "node_uuid": "<node_uuid>"
    },
    "name": "search_images_by_node"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Zero-indexed page number for pagination. Defaults to 0 (first page).
`node_uuid`	Yes	The UUID of the phylogenetic node to find images for.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full disclosure burden, and it does cover the most consequential behavioral trait: results are limited to images that *directly* represent the node, not descendants, and only 'silhouette' images are returned. It is silent on read-only guarantees, return payload shape, and empty-result behavior, which keeps it short of a 5.

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?

Three sentences, front-loaded with the action and scope, then the use case, then the alternative. Every sentence earns its place and none restates the schema.

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 two-parameter list tool with no output schema, the description covers purpose, usage, and sibling routing adequately. It does not mention pagination behavior or what an image result contains, which is a minor but real gap given there are no annotations to fill in.

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 description coverage is 100% – both node_uuid (UUID of the phylogenetic node) and page (zero-indexed pagination) are documented in the schema itself. The description adds no format, constraint, or default detail beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('List silhouette images'), the precise scope ('directly represent a specific phylogenetic node'), and gives a concrete example (all images of Homo sapiens). It is immediately distinguishable from search_images_by_clade, which the description names explicitly.

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?

Gives both the when-to-use ('find all images of a particular taxon') and the when-to-use-the-alternative condition ('For ancestral nodes, consider using search_images_by_clade instead to get images of all descendant taxa as well'). Routing between the two siblings is fully specified rather than left to inference.

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

Deploy Server