Skip to main content
Glama

Stat Make Dataframe

stat_make_dataframe

Build a DataFrame from a {column: [values]} mapping to create hypothetical data for worked examples, sanity checks, and method illustrations, not real analysis.

Instructions

Build a DataFrame from a {column: [values]} mapping.

Use this for worked examples, sanity checks, and illustrating a method with hypothetical data.

When NOT to use: never for real analysis — fabricated data must not enter an analysis of real results.

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": {
      "name": "<name>",
      "columns": "<columns>"
    },
    "name": "stat_make_dataframe"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
columnsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the defining behavioral trait (data is fabricated, so results are synthetic and must not contaminate real analysis). It does not disclose what actually happens on creation — whether the frame is registered under the given name in a session, how it is later referenced, or whether repeated names collide.

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?

Three short blocks with zero filler: the operation and input shape first, intended uses second, prohibition last. Front-loaded and skimmable, every sentence earning its place.

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?

An output schema exists, so return values need not be described, and the critical safety constraint is stated. However, for a tool whose whole point is producing a named object, the unexplained 'name' parameter leaves an agent guessing about how to reference the resulting DataFrame in later calls.

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

Parameters2/5

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

Schema coverage is 0%, so the description must supply meaning for both required parameters. It explains the value side well ({column: [values]} mapping) but says nothing about the required 'name' parameter — whether it is a label, a session handle, or must be unique — leaving half the contract undocumented.

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 ('Build a DataFrame') and gives the exact input shape ({column: [values]}), which is concrete enough to distinguish it from data-loading siblings. It stops short of naming a sibling such as stat_load_data for real data, so the contrast is implied rather than stated.

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?

Explicitly enumerates intended uses (worked examples, sanity checks, illustrating a method with hypothetical data) and adds a hard 'When NOT to use' clause forbidding real analysis. The only gap is that no concrete alternative tool is named for the real-data case, though the exclusion itself is unambiguous.

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