Skip to main content
Glama
Sign In
vCFD

vCFD

by gpu7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

generate_mesh

Run blockMesh to generate a computational mesh for OpenFOAM simulations, with optional background execution for asynchronous processing.

Instructions

Run blockMesh for the case. Use background=true for async job.

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": {
      "case_name": "<case_name>"
    },
    "name": "generate_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_nameYes
backgroundNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the core action (running blockMesh) and the async option for background, but does not detail side effects, failure behavior, or prerequisites such as the case already existing.

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, front-loaded sentences deliver the core action and the async hint without any waste. Every word earns 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?

For a simple tool, the description covers the basic operation and the async option, but it lacks explicit guidance on when to use it relative to sibling tools and prerequisites like the case needing to exist. An output schema exists, so return value details are not required, but other context gaps remain.

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?

The description adds meaning to background by explaining it enables async jobs, which is beyond the schema's bare boolean. However, case_name is not explicitly described, though 'for the case' implies its role. Schema coverage is 0%, so the description partially compensates.

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?

The description clearly states the tool runs blockMesh for a given case, using a specific verb and resource. This distinguishes it from sibling tools like check_mesh (which checks the mesh) and start_solver (which runs the solver).

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 description mentions using background=true for async jobs, offering a conditional usage hint. However, it does not explicitly say when to use this tool versus alternatives or mention any prerequisites/exclusions.

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