Skip to main content
Glama
Sign In
surfer-mcp

surfer-mcp

by office31
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_grid

Interpolates XYZ point data from CSV, TSV, or text files into a binary Surfer grid (.grd), with configurable gridding algorithms, grid dimensions, and column mappings.

Instructions

Interpolate XYZ point data into a binary Surfer grid (.grd).

Args: data_file: CSV, TSV or whitespace text file containing X, Y, Z columns. output_grid: Destination .grd path (workspace-relative or absolute). Defaults to grids/.grd. x_col: 1-based X column. y_col: 1-based Y column. z_col: 1-based Z column. algorithm: Gridding algorithm; kriging by default. cols: Grid columns (10-4000). rows: Grid rows (10-4000).

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": {
      "data_file": "<data_file>"
    },
    "name": "create_grid"
  }
}

Input Schema

NameRequiredDescriptionDefault
colsNo
rowsNo
x_colNo
y_colNo
z_colNo
algorithmNokriging
data_fileYes
output_gridNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. It reveals the default output path (grids/<name>.grd) but says nothing about overwriting an existing .grd, whether the Surfer application must be open, runtime for large grids, or failure modes for malformed input.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A front-loaded purpose sentence followed by a compact per-argument list. Every line maps to a parameter, with no filler, though the raw docstring 'Args:' formatting is slightly rough.

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?

The output schema covers return values, and the Args block covers all eight parameters, so an agent can construct a call. What is missing is operational context: overwrite behavior, application-state requirements, and column format edge cases.

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 0%, and the Args block usefully supplies the 1-based column convention, the 10-4000 bounds on cols/rows, and the kriging default. However it omits the accepted algorithm values (only an enum in the schema lists them), the default rows/cols of 300, and the file format expectations beyond headerless X/Y/Z columns.

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?

The first sentence names a specific verb and resource: interpolate XYZ point data into a binary Surfer grid (.grd). That is clearly distinct from siblings such as create_contour_map and create_surface_map, though the description never explicitly contrasts with them.

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?

It never states when to choose this over create_surface_map or create_contour_map, nor any prerequisites such as whether Surfer must be running or where data_file must live. Usage is only inferable from the tool's name.

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