Skip to main content
Glama
Sign In

FERS — structural FEM

by com.ferscloud
OverviewDiscussionsAdmin

Save a model to your account

save_model

Save a model to your FersCloud account (requires a Pro subscription; free accounts use local JSON export/import instead). Solver results are never stored. Returns the model id.

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

Input Schema

NameRequiredDescriptionDefault
nameYesA name for the saved model
modelNoStringified FERS model JSON
model_refNoHandle from stash_model, used INSTEAD of `model`. Avoids sending the whole document on every step; the tool returns the same handle back.
descriptionNoOptional description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses a subscription prerequisite, an explicit data-exclusion rule (solver results never stored), and the return value ("Returns the model id") — all information the annotations cannot convey. It does not say whether saving under an existing name overwrites or creates a duplicate, which matters given idempotentHint=false, but the added context is substantial.

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 sentences, front-loaded with the action and account target, then the eligibility caveat and the persistence exclusion. No filler; every clause carries a distinct constraint.

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?

With no output schema, the description usefully states it returns the model id, and the Pro-subscription gating is a real behavioral constraint an agent must know before calling. The only gap is duplicate/overwrite behavior for repeated saves with the same name.

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 itself explains the model/model_ref trade-off in detail, so the baseline applies. The description adds no parameter-level information of its own beyond noting that a model id comes back.

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?

"Save a model to your FersCloud account" states a specific verb and resource, and the parenthetical scopes what is and is not persisted ("Solver results are never stored"). It does not contrast itself with the close sibling stash_model, which also produces a stored handle, so the agent must infer the save-vs-stash distinction from the schema rather than the description.

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 description gives an explicit eligibility condition ("requires a Pro subscription") and a routing rule for the ineligible case ("free accounts use local JSON export/import instead"), which is exactly the kind of when/when-not guidance agents need. It stops short of naming a sibling tool as the alternative, so it's clear context but not full alternative routing.

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

All FERS — structural FEM 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