Skip to main content
Glama

np_camera_capture

Capture the last camera image from a selected MEA (1-5) on the NeuroPlatform, returning viability and descriptor data.

Instructions

NeuroPlatform v2 — Last MEA camera capture (descriptor + viability)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meaNoMEA selector [1-5]
Behavior2/5

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

No annotations are provided, and the description does not disclose whether the tool performs a capture (side effect) or retrieves an existing capture. It also lacks information about permissions, failure modes, or return behavior beyond a vague hint of 'descriptor + viability'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short and front-loaded, but the brevity borders on under-specification. There is no wasted wording, but the cryptic phrasing 'Last MEA camera capture' and parenthetical output list are not sufficiently explanatory.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has only one well-documented parameter, but no output schema and no annotations. The description offers only a vague output hint and fails to clarify the exact action, return values, or applicable scenarios, leaving important gaps for a simple but under-specified tool.

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?

The input schema fully documents the 'mea' parameter with range and default, providing 100% coverage. The description adds no extra meaning about the parameter, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies an MEA camera capture operation, but the phrase 'Last MEA camera capture (descriptor + viability)' is ambiguous about whether it captures a new image or retrieves the most recent one. It does not clearly distinguish this tool from sibling np_* tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/christophejlegros-lgtm/ASTRA-Unified-ResearchLab-MCP-v2.5'

If you have feedback or need assistance with the MCP directory API, please join our Discord server