Skip to main content
Glama
Sign In
PT5 MCP Server

PT5 MCP Server

by doudoufu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_pt5_samples

Retrieve current (mA) and voltage (V) samples from a PT5 power measurement file. Optionally filter by time range and decimate to reduce data points.

Instructions

Retrieve sample data from a PT5 file, with optional time range filtering and sample decimation. Returns current (mA) and voltage (V) values.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file_path": "<file_path>"
    },
    "name": "get_pt5_samples"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsolute path to the .pt5 file
start_time_secNoStart time in seconds (default: 0)
end_time_secNoEnd time in seconds (default: end of capture)
decimationNoReturn every Nth sample (default: 1). Use 10, 100, 1000 for large files.
max_samplesNoMaximum number of samples to return (default: 5000).

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?

No annotations are provided, so the description carries full burden. It mentions retrieval and output units but does not disclose error behavior, performance implications, or whether it is read-only (implied by 'retrieve' but not explicit). The decimation hint is in the schema, not the description.

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 two sentences, immediately stating the core purpose and return values. Every word is functional, with no redundancy or unnecessary detail. It is well-structured and front-loaded.

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?

Given 5 parameters, no output schema, and no annotations, the description covers the purpose and key options but lacks details on return format (e.g., array, object), error handling, or limits. It is adequate for a straightforward tool but not comprehensive.

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?

Schema coverage is 100%, providing good parameter descriptions. The tool description adds value by summarizing the optional filtering and decimation, and by stating the return units (mA, V), which are not in the schema. This enhances the agent's understanding beyond the schema alone.

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 clearly states the tool retrieves sample data from a PT5 file with optional time range filtering and decimation, and specifies the return values (current and voltage). It distinguishes itself from sibling tools like get_pt5_header (metadata) and analyze_pt5_trend (analysis).

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 implies usage for raw data retrieval with filtering options but does not explicitly compare to siblings or state when to avoid using it. The context signals list sibling tools, but the description lacks direct guidance on alternative selection.

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