Aman-Amith-Shastry-scientific_computation_mcp

plot_vector_field

Read-onlyIdempotent

    Plots a 3D vector field from a string "[u(x,y,z), v(x,y,z), w(x,y,z)]"

    Args:
        f_str: string representation of 3D field, e.g. "[z, -y, x]".
        bounds: (xmin, xmax, ymin, ymax, zmin, zmax)
        n: grid resolution per axis

    Returns: Displayed Matplotlib 3D quiver plot (no image return needed)

Input Schema

TableJSON Schema

Name	Required	Description
`n`	No	Number of arrows sampled per axis; the grid holds n**3 points.
`f_str`	Yes	3D vector field in bracketed list form, e.g. "[z, -y, x]".
`bounds`	No	Plot domain as (xmin, xmax, ymin, ymax, zmin, zmax).

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 10, 2026

addedInput schema / properties / bounds / description

Added value: +"Plot domain as (xmin, xmax, ymin, ymax, zmin, zmax)."

addedInput schema / properties / bounds / maxItems
```
Added value: +6
```
addedInput schema / properties / bounds / minItems
```
Added value: +6
```

addedInput schema / properties / bounds / prefixItems

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "number"
+  }
+]

changedInput schema / properties / bounds / title

Previous value: -"bounds"New value: +"Bounds"

changedInput schema / properties / bounds / type

Previous value: -"string"New value: +"array"

addedInput schema / properties / f_str / description

Added value: +"3D vector field in bracketed list form, e.g. \"[z, -y, x]\"."

addedInput schema / properties / n / description

Added value: +"Number of arrows sampled per axis; the grid holds n**3 points."

addedInput schema / properties / n / maximum
```
Added value: +30
```
addedInput schema / properties / n / minimum
```
Added value: +2
```

First observedJan 31, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds useful behavioral detail: the tool displays a Matplotlib 3D quiver plot and does not return an image. This goes beyond what the annotations provide without contradicting them.

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?

Compact docstring with a clear one-sentence purpose, an Args list, and a Returns note. No unnecessary prose, though the Args section is partially redundant with the schema's parameter descriptions.

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?

For a simple read-only plotting tool, the description covers the input format, grid resolution, bounds, and return behavior (displayed plot, no image return). All essential information for calling it correctly is present; error handling of malformed strings is not described but is not critical for basic use.

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 description coverage is 100% and the schema already explains each parameter (f_str format, bounds tuple, n resolution). The description's Args section restates these but adds no new information beyond the schema, so the baseline score of 3 applies.

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 ('Plots') and resource ('3D vector field'), and includes an example expression. Clearly distinguishes itself from siblings like plot_function, which presumably handles scalar functions, by emphasizing the 3D vector field input.

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?

The first sentence gives clear context for when to use this tool: when a 3D vector field needs to be visualized. It does not explicitly name alternatives or exclusion criteria, but the purpose statement is specific enough to guide selection.

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

All Aman-Amith-Shastry-scientific_computation_mcp tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

plot_vector_field

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources