Skip to main content
Glama
Sign In
ASTRA

ASTRA

by christophejlegros-lgtm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

np_query_triggers

Read-onlyIdempotent

Query triggers sent to an organoid over a configurable time window, with optional deduplication to keep only up==1 transitions.

Instructions

NeuroPlatform v2 DB — TriggersQuery: triggers sent to the organoid over a window

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_query_triggers"
  }
}

Input Schema

NameRequiredDescriptionDefault
dedupNoKeep only up==1 transitions (drop duplicates)
window_secNoLook back this many seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only that this is a DB query over a window; it does not describe return format, pagination, or any rate/auth constraints. With annotations carrying the safety load, a 3 is appropriate.

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

Conciseness4/5

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

A single front-loaded sentence with no wasted words. The internal 'NeuroPlatform v2 DB — TriggersQuery:' prefix is slightly redundant with the annotation title but does not obscure the meaning.

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

Completeness3/5

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

Simple read-only query with two fully described parameters and strong safety annotations, so an agent can invoke it. However, no output schema exists and the description never hints at the return shape (e.g., list of triggers, timestamps), leaving some inference to the agent.

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 description coverage is 100%, so both parameters (dedup, window_sec) are fully documented in the schema. The description merely echoes the window concept without adding syntax or behavioral nuance beyond the schema. Baseline 3 applies.

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

Purpose4/5

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

States a specific verb (query) and resource (triggers sent to the organoid) with scope (over a window). This implicitly distinguishes it from np_send_trigger, but no sibling tool is named for explicit differentiation.

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 when-to-use, when-not, or alternative guidance is provided. The agent can infer it retrieves historical trigger data from the purpose, but there is no explicit routing 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