Skip to main content
Glama
Sign In
PPK2 MCP Server

PPK2 MCP Server

by andy-qingcai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

start_capture

Starts a long, non-blocking background capture for PPK2 current and logic data, even beyond 60s; check progress, then stop to save samples.

Instructions

启动长采集(后台,不阻塞;可>60s)。之后用 get_capture_status 查看, stop_capture 结束并落盘。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavioral trait: the operation is asynchronous, background, non-blocking and may run longer than 60s. It also implies the data lands on disk only when stop_capture is called. However, it says nothing about error conditions (e.g. a capture already running), permissions, or what happens to any in-progress capture.

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?

Two compact sentences with zero filler, front-loading the operation and its async nature before the follow-up tool routing. Nothing could be removed without losing meaning.

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

Completeness4/5

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

For a zero-parameter tool with no output schema and no annotations, the description supplies the essential context: async execution, expected duration, and the start/status/stop lifecycle. Missing only edge-case behavior for repeated invocation, which would round it out fully.

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 schema accepts zero parameters, so there is no argument semantics to explain; the baseline for a parameterless tool applies. The description correctly adds no redundant parameter talk.

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 ('start a long capture') and immediately adds the defining traits (background, non-blocking, can exceed 60s). It clearly separates itself from stop_capture/get_capture_status by naming them as the follow-up steps, though it does not explicitly contrast with the ambiguous 'capture' sibling.

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

Usage Guidelines4/5

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

Provides explicit workflow routing: start here, then use get_capture_status to poll, then stop_capture to finish and persist. This tells the agent when to reach for the neighboring tools. It stops short of stating the condition under which the plain 'capture' sibling should be chosen instead.

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