Skip to main content
Glama
Sign In
ASTRA

ASTRA

by christophejlegros-lgtm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

sensor_status

Read-onlyIdempotent

Returns the status of the multimodal sensor pipeline, letting AI assistants check sensor health and availability in ASTRA before running simulations.

Instructions

Multimodal Sensor Pipeline 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": "sensor_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.4/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 fully covered by structured data. The description contributes nothing beyond that — no information about what the pipeline status comprises, whether it is cheap or expensive, or how fresh the reading is — so it adds no value over the annotations.

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 a single short phrase with no wasted words, so it is structurally lean. However, brevity here comes from under-specification rather than disciplined concision — it is a title, not a description.

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?

For a no-parameter status tool in a large cluster of overlapping status/probe tools, an agent needs to know what this status covers and how it differs from get_system_status or np_status. No output schema exists to fill the gap, and the description provides no scope or return-value context.

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 nothing for the description to disambiguate. Baseline 4 applies; no parameter-related gaps exist.

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 is essentially a restatement of the name and title ('Multimodal Sensor Pipeline Status'), with no verb and no indication of what is actually returned or checked. It does not distinguish this tool from the many sibling status tools such as get_system_status, np_status, wm_status, or ovo_status.

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?

There is no guidance on when to call this versus the other status/probe tools in the cluster; the 'status' framing implies a read of pipeline health but nothing more. No prerequisites, no when-not-to-use, no alternative named.

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