Skip to main content
Glama

convert_statistics

Convert R, MATLAB, SPSS, Stata, and SAS statistical files into JSON or CSV for cross-platform analysis.

Instructions

Convert statistical data formats: R data (.rdata, .rds)→JSON, MATLAB (.mat)→JSON, SPSS (.sav)→JSON, Stata (.dta)→JSON. Note: Binary formats require Python libraries (pyreadstat, scipy).

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": {
      "inputPath": "<inputPath>",
      "outputPath": "<outputPath>"
    },
    "name": "convert_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputPathYesAbsolute path to input statistical file
outputPathYesAbsolute path for output file (include extension)
inputFormatNoInput format (auto-detected if not provided)
outputFormatNoOutput format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that binary formats need pyreadstat/scipy, which is real behavioral context, but says nothing about file overwrite behavior, failure modes, or whether conversion preserves metadata.

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 short sentences with zero padding; the format mapping is front-loaded and the caveat follows logically.

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?

There is no output schema and no annotations, so the description must stand in for behavior. It covers source formats and dependencies adequately but omits output-format choices, path/overwrite semantics, and error expectations for a tool that writes files.

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 100%, so inputs, outputs, and enums are already documented. The description adds a format-dependency note but does not mention the supported 'csv' output or 'sas7bdat' input that the schema exposes, so it adds little beyond the schema.

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?

States a specific verb (convert) plus the exact resource class (statistical data formats) and enumerates the concrete source formats (.rdata, .rds, .mat, .sav, .dta) with their target. This makes it immediately distinguishable from siblings like convert_spreadsheet or convert_dev_format.

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 format list implies when the tool applies, and the dependency note gives a practical prerequisite. However, it never states when to pick this over a sibling converter or what happens if the required Python libraries are absent beyond a bare warning.

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