Skip to main content
Glama
Sign In

MDEngine

by com.forcefieldsilicon
OverviewDiscussionsAdmin

Start here: guides by customer type

guide
Read-onlyIdempotent

No key needed. Without customer_type: the list of guides (one line each), the start page and how to get a key. With customer_type (mineral-processing | dark-proteins | alloys): the full guide, which says what to supply, what runs, what comes back and what it costs. With template (openmm-stability): the script text of that template, ready to save and submit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateNoopenmm-stability (dark-proteins stage 1 OpenMM script); returns the script text
customer_typeNomineral-processing | dark-proteins | alloys; omit for the list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / customer_type / description
      Previous value: -"mineral-processing | dark-proteins; omit for the list"New value: +"mineral-processing | dark-proteins | alloys; omit for the list"
  2. Changed1 schema field changed
    • addedInput schema / properties / template
      Added value: +{
+  "description": "openmm-stability (dark-proteins stage 1 OpenMM script); returns the script text",
+  "type": "string"
+}
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Adds information the annotations cannot carry: 'No key needed' (an auth requirement, notable given the rest of the API presumably needs one) and the exact return shape per mode ('one line each', 'script text, ready to save and submit'). With no output schema, this is exactly the disclosure an agent needs.

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 dense sentences, each covering one mode, with the surprising fact ('No key needed') front-loaded. No filler, no repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by describing the return content for all three modes. An agent can decide which mode to call and know what it will get back without further information.

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

Parameters4/5

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

Schema coverage is 100%, so the parameter names and enum values are already documented. The description adds meaning beyond that by explaining what each value actually produces ('the full guide, which says what to supply, what runs, what comes back and what it costs'), though it partially restates the enum values already in the schema.

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 description makes clear this is a documentation/guide retrieval tool and spells out precisely what each call mode yields (guide list, full guide, or template script text). It does not explicitly name a sibling or state 'not for submitting jobs', but the content is unmistakably distinct from the job-management siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit branching guidance: omit customer_type for the list, pass customer_type for the full guide, pass template for the script text. Each mode's trigger and outcome are stated, leaving nothing to inference.

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

All MDEngine toolsInspect
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.

Resources