Skip to main content
Glama
wzlwww

baltamatica.mcp

by wzlwww
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
execute_codeC

Execute a Baltamatica code snippet and return output from the backend.

run_scriptB

Run a local Baltamatica .m script file.

clear_workspaceB

Clear variables from the Baltamatica workspace state.

list_variablesA

List variables in the Baltamatica workspace state.

get_variableB

Return a display representation of one Baltamatica variable.

set_variableA

Create or overwrite a workspace variable.

data may be a number, a boolean, a 1-D list (row vector), or a 2-D nested list (matrix). Without dtype, numbers become double and booleans become logical. dtype may request an integer type (int8..uint64), float32/float64, or a complex type (complex64/complex128, with data={"real": <array>, "imag": <array>}).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a distinct purpose: workspace management (clear, list, get, set) and code execution (snippet vs script). No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (e.g., clear_workspace, execute_code, set_variable). No deviations.

Tool Count5/5

6 tools is well-scoped for a MATLAB-like environment, covering workspace operations and code execution without unnecessary bloat.

Completeness4/5

Covers core workspace CRUD (create via set, read via get/list, delete via clear) and execution. Missing a per-variable delete, but overall sufficient for typical use.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources