Skip to main content
Glama
getsimba-ai

Simba MCP Server

Official
by getsimba-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Rename Model

rename_model
DestructiveIdempotent

Rename a model and/or declare its money currency. Pass name, currency or both.

Instructions

Rename a model and/or declare its money currency. Pass name, currency or both.

The model's saved/unsaved state is untouched (use save_model to file it into a project). The name is HTML-sanitized server-side and must be non-empty.

The currency labels the model's spend and money outcomes everywhere (results, optimiser and scenario runs, PDFs). It changes nothing fitted, so there is no refit. Only the model's owner may set it, and only on a completed model. Refused (409) for a model that is study evidence (change it in a revision of the recipe), for one whose campaign curves were built in another currency, and for one with old-format settings. Never guess a currency: use the one the user or the data states.

Args: model_hash: Hash of the model. name: New display name; leave empty to keep the current one. currency: Uppercase code: GBP, USD, EUR, CAD, AUD, NZD, CHF, SGD, HKD, JPY, KWD, BHD or OMR. Leave empty to keep the current one.

Input Schema

NameRequiredDescriptionDefault
nameNo
currencyNo
model_hashYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.18.0
    • addedInput schema / properties / currency
      Added value: +{
+  "default": "",
+  "title": "Currency",
+  "type": "string"
+}
    • addedInput schema / properties / name / default
      Added value: +""
    • changedInput schema / required
      Previous value: -[
-  "model_hash",
-  "name"
-]New value: +[
+  "model_hash"
+]
  2. Changed1 schema field changedv0.5.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "rename_modelDictOutput",
+  "type": "object"
+}
  3. First observedv0.3.2

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: saved/unsaved state untouched, server-side HTML sanitization, non-empty name requirement, owner-only authorization, completed-model requirement, no-refit consequence, and a full set of 409 refusal conditions. This is exactly the behavioral depth a mutation tool needs and it does not contradict the destructiveHint/idempotentHint annotations.

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?

Front-loads purpose and the alternative in the first two sentences, then layers refusals and arg documentation. Every sentence carries information, though the dedicated Args block partially restates what could be folded in, making it slightly longer than strictly necessary.

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?

An output schema exists, so return values need not be explained. For a mutation tool with rich annotations, the description fully covers authorization, preconditions, side effects, and failure modes — nothing an agent needs to invoke it correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does so: name semantics (empty keeps current, HTML-sanitized, non-empty), currency as an uppercase code with an explicit list of valid values, and empty-means-unchanged for both. model_hash is also explained.

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 and resource ('Rename a model and/or declare its money currency') and immediately distinguishes the operation from a sibling by pointing to save_model for the filing action. An agent can tell exactly what this tool does and does not do.

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?

Explicit routing ('use save_model to file it into a project'), explicit parameter guidance ('Pass name, currency or both'), and explicit negative guidance ('Never guess a currency: use the one the user or the data states'). It also enumerates the conditions under which the call is refused.

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