ASTRA Unified Research Lab MCP Server

np_camera_capture

Capture the latest MEA camera feed (1-5) to retrieve descriptor and viability data for NeuroPlatform v2.

Instructions

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

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": "np_camera_capture"
  }
}

Input Schema

Name	Required	Description	Default
`mea`	No	MEA selector [1-5]

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0Aug 17, 2026

TDQS

C2.2/5.0

Behavior2/5

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

With no annotations, the description must fully disclose behavior, but it only hints at the output ('descriptor + viability'). It does not state whether the operation is read-only or has side effects, nor does it mention permissions, rate limits, or failure modes.

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

Conciseness2/5

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

The description is extremely short, but it is under-specified rather than concise. It reads as a fragment and omits essential information such as the action performed, making it less useful despite its brevity.

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?

Without an output schema, the description should explain what 'descriptor + viability' means in return terms, but it does not. It also fails to clarify whether this is a capture or retrieval operation, leaving major gaps in understanding the tool's purpose and behavior.

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% for the single parameter 'mea', which is fully described with constraints and default. The tool description adds no additional parameter meaning, but the schema already handles it, so baseline 3 is appropriate.

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

Purpose2/5

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

The description lacks a clear verb; 'Last MEA camera capture' is a noun phrase, so it's unclear whether the tool performs a capture or retrieves the last capture. It mentions the resource (MEA camera) and output (descriptor + viability), but does not explicitly state the action or distinguish from sibling tools like sensor_visual.

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 provided on when to use this tool versus alternatives. There is no mention of prerequisites, use cases, or exclusions, leaving the agent without context for selecting it appropriately.

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

Deploy Server