px4-flight-debugger

Overview Schema Source Related Servers Discussions Admin

list_logs

List PX4 flight logs newest first with local start times, or find the log covering a specific wall-clock time by day or timestamp.

Instructions

List flight logs newest first with their local start time, or find the one that covers a given wall-clock time.

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

Input Schema

Name	Required	Description
`at`	No	local time 'HH:MM[:SS]' (today) or 'YYYY-MM-DD HH:MM' to find the log running then
`day`	No	only logs started on this local date, 'YYYY-MM-DD'
`limit`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses ordering (newest first) and that times are local/wall-clock, but says nothing about permissions, pagination, default limit behavior, or what happens when no log matches.

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

Conciseness5/5

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

One sentence, front-loaded with the primary action and appended with the alternate mode. No filler, every clause carries information.

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?

Output schema exists so return values need not be explained, and the two modes are covered. However, for a tool with zero annotations, missing guidance on the undocumented 'limit'/pagination behavior and on distinguishing it from sibling log tools leaves notable gaps.

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 67% (the limit parameter is undocumented). The description clarifies the 'at' parameter's semantics (finding the log running at a wall-clock time) beyond the schema, and implies ordering, but adds nothing for 'day' or 'limit'. Baseline is appropriate given the schema does most of the work.

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 and resource ('List flight logs') plus the ordering ('newest first') and a secondary mode ('find the one that covers a given wall-clock time'). It is clear what the tool does, though it never references any of the many siblings (log_summary, scan_logs, log_messages) that could also surface logs.

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

Usage Guidelines3/5

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

The two implicit modes (list all vs. find the log covering a time) are implied by the sentence, but there is no explicit when-to-use rule, no when-not condition, and no routing to alternatives like scan_logs or log_messages. The agent can infer usage but not with confidence.

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

Deploy Server