Skip to main content
Glama
zhixuan2333

PPK2 MCP Server

by zhixuan2333

ppk2_logic

Capture and analyze digital logic signals on 8 channels (D0–D7) using the PPK2. Returns per-channel statistics including high fraction, edge count, and level transitions, with optional downsampled series.

Instructions

Capture the PPK2's 8 digital logic channels (D0–D7) — a logic analyser.

The PPK2 samples 8 digital inputs alongside current at ~100k samples/s. This starts sampling, discards a settling window, collects digital states for duration_seconds, and returns per-channel statistics: the fraction of time each channel was high, the number of edges (level transitions), and the first/last observed level. Requires a prior ppk2_configure.

Note: unconnected digital pins float and may read a constant or noisy level; drive them from your DUT to see real activity.

Args: duration_seconds: Capture window after settling. 0.05–60. settle_ms: Initial samples discarded before timing starts. Default 100 ms. channels: Which channels (0–7) to report. Default all eight. include_series: If true, also return a downsampled level series per channel (each point is the fraction high over that block, 0.0–1.0). series_points: Target number of points in each downsampled series.

Returns sample count, achieved sample rate, and a channels map keyed by channel index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
duration_secondsNo
settle_msNo
channelsNo
include_seriesNo
series_pointsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description details the sampling process: starts sampling, discards a settling window, collects states for duration, and returns statistics. It also warns about unconnected pins floating. With no annotations, this provides reasonable behavioral context, though it does not state whether it is read-only or if it affects concurrent measurements.

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?

The description is well-structured: a one-sentence purpose, followed by process explanation, a behavioral note, and a labeled Args list. Every sentence adds value, with no redundancy, fitting within a moderate length.

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

Completeness5/5

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

The description covers the prerequisite (ppk2_configure), the sampling process, parameter details, output structure (sample count, sample rate, channels map), and a behavioral note on floating pins. Given the presence of an output schema, this fully equips an agent to use the tool correctly.

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

Parameters5/5

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

The description explains all five parameters: duration_seconds range (0.05–60), settle_ms default (100 ms), channels (0–7, default all), include_series (if true returns downsampled series), and series_points (target points). This adds significant meaning beyond the bare schema, which has no descriptions.

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

Purpose5/5

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

The description opens with a clear verb 'Capture' and specific resource 'PPK2's 8 digital logic channels (D0–D7)', immediately distinguishing it from sibling tools like ppk2_measure which focus on current/power. The mention of 'logic analyser' reinforces its purpose.

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 description states 'Requires a prior ppk2_configure', providing a necessary prerequisite. However, it does not explicitly advise when to use this tool over alternatives (e.g., ppk2_measure for current-only analysis) or when not to use it. The context with siblings implies differentiation, but explicit guidance is missing.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zhixuan2333/PPK2-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server