Skip to main content
Glama
Sign In
ASTRA

ASTRA

by christophejlegros-lgtm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

get_system_status

Read-onlyIdempotent

Retrieve the current operational status of the ASTRA bio-hybrid neuromorphic simulation pipeline and its related services.

Instructions

ASTRA System Status

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds nothing beyond the title — no indication of what the status covers, whether it is cached, or how it relates to other status tools.

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 single fragment is short but this is under-specification, not conciseness. There is no front-loaded statement of purpose or scope to anchor the agent.

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?

There is no output schema and no parameters, so the description carries the entire burden of explaining what status data is returned and at what granularity. It says nothing, leaving an agent unable to predict the return content in a crowded namespace of status tools.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics burden and the baseline is 4 per the rubric. There is nothing for the description to document here.

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 'ASTRA System Status' merely restates the tool name/title without a verb or any indication of what status means here. With siblings like get_metrics, get_platform_status, ovo_status, wm_status, np_status, and sensor_status, there is no way to distinguish this tool's scope from theirs.

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

Usage Guidelines1/5

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

The description contains no guidance whatsoever on when to use this tool versus the many sibling status/metrics tools. Nothing indicates prerequisites, context, or alternatives.

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