Skip to main content
Glama
Sign In
scpi-mcp

scpi-mcp

by armchairdeity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

capture_memory

Captures the deep-memory full sample-rate waveform for one analog channel. Returns sample data or a summary with point count and time range.

Instructions

Capture the deep-memory waveform for one channel (full sample-rate record).

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": {
      "channel": "<channel>"
    },
    "name": "capture_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsNoNumber of deep-memory sample points to read back. None reads the full acquisition record.
channelYesAnalog channel to read, 1-based (1–4).
include_samplesNoIf True, include the full time/volts sample arrays. Default False returns only a summary (point count, sample rate, start/end time) to avoid flooding the context.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.1
    • removedInput schema / properties / args
      Removed value: -{
-  "title": "Args"
-}
    • addedInput schema / properties / channel
      Added value: +{
+  "description": "Analog channel to read, 1-based (1–4).",
+  "title": "Channel",
+  "type": "integer"
+}
    • addedInput schema / properties / include_samples
      Added value: +{
+  "default": false,
+  "description": "If True, include the full time/volts sample arrays. Default False returns only a summary (point count, sample rate, start/end time) to avoid flooding the context.",
+  "title": "Include Samples",
+  "type": "boolean"
+}
    • removedInput schema / properties / kwargs
      Removed value: -{
-  "title": "Kwargs"
-}
    • addedInput schema / properties / points
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Number of deep-memory sample points to read back. None reads the full acquisition record.",
+  "title": "Points"
+}
    • changedInput schema / required
      Previous value: -[
-  "args",
-  "kwargs"
-]New value: +[
+  "channel"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "capture_memory_implDictOutput",
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It only states the high-level action and lacks details about side effects, permissions, data volume implications, or what happens to existing recordings.

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 a single concise sentence with no extraneous words. It efficiently conveys the core purpose without redundancy.

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

Completeness2/5

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

Despite the tool having a complex output and being used for data capture, the description omits any mention of return values or output schema. It does not explain that the output includes either full sample arrays or a summary, leaving the agent to infer from the schema alone.

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?

The input schema provides descriptions for all three parameters (100% coverage). The description adds no additional parameter-level context beyond the schema, so a baseline score of 3 is appropriate.

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 verb 'capture' and the resource 'deep-memory waveform for one channel' with the detail 'full sample-rate record'. It distinguishes itself from sibling tools like capture_screen or capture_aligned by specifying deep-memory and per-channel operation.

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?

The description provides no guidance on when to use this tool versus alternatives such as capture_aligned or capture_screen. There is no mention of prerequisites, context, or exclusions.

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