Skip to main content
Glama
Sign In
neurochat

neurochat

by AyushXRane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

navigate

Move the crosshair to a specific atlas region or to explicit coordinates in a brain volume. Accepts region labels or [x,y,z] coordinates in millimeters.

Instructions

Move the crosshair to a named atlas region or to explicit coordinates.

Exactly one of region_label or coords. A region_label must exist in the loaded atlas; a near-miss returns suggestions and moves nothing. Coordinates are accepted only from you or the user, and the space they were read in is echoed back.

Args: region_label: Label from the loaded atlas, e.g. "Left Hippocampus". coords: [x, y, z] in millimetres. space: Space for coords, e.g. "MNI152NLin6Asym". Defaults to the volume's space. volume: Which loaded volume to interpret against. Defaults to the most recent.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
spaceNo
coordsNo
volumeNo
region_labelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Despite no annotations, the description fully discloses mutual exclusivity, error handling (near-miss returns suggestions, moves nothing), coordinate source restrictions, and default values for space and volume.

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 concise with a clear summary, usage paragraph, and well-labeled Args section. Every sentence adds meaningful information without redundancy.

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 no output schema and simple side-effect behavior, the description covers usage, defaults, and error cases. Minor missing detail about visual feedback does not detract significantly.

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

Parameters5/5

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

With 0% schema coverage, the description fully documents all four parameters with examples, units, and defaults, adding significant value beyond the bare schema.

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 moves the crosshair to a named atlas region or explicit coordinates, and it distinguishes from sibling tools like load_atlas and load_volume.

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 specifies that exactly one of region_label or coords must be used, explains behavior for near-misses, and notes coordinate source restrictions. It lacks explicit comparison to alternatives like list_regions but is sufficient for its context.

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

Deploy Server

Other Tools