Simba MCP Server

Official

by getsimba-ai

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

Set Run Pinned

set_run_pinned

DestructiveIdempotent

Pin or unpin a saved optimizer or scenario run to control its visibility. Idempotent operation allows safe re-runs without side effects.

Instructions

Pin or unpin a saved optimizer or scenario run.

Declarative and idempotent: setting the current state again is a no-op, so scripts can safely re-run it.

Args: artifact: "optimizer" (run_id "opt_...") or "scenario" ("scn_..."). model_hash: Hash of the model the run belongs to. run_id: The run's stable id from run history. pinned: Desired pin state.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pinned`	Yes
`run_id`	Yes
`artifact`	Yes
`model_hash`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.5.0Sep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "set_run_pinnedDictOutput",
+  "type": "object"
+}

First observedv0.3.2Aug 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint, readOnlyHint, and idempotentHint. The description adds specificity by explaining that setting the current pin state again is a no-op and that scripts can safely re-run it, which goes beyond the bare hint. It does not detail what happens when unpinning, but the annotation covers the destructive nature.

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?

The description is compact, front-loaded with the purpose, and organized into a short declarative statement and a clear Args list. Every sentence contributes either to use intent, behavioral guarantees, or parameter understanding.

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?

For a four-scalar-parameter tool with an output schema and idempotency/destructive annotations, the description covers all the information needed to invoke it correctly: accepted artifact types, id semantics, model association, and the pin state. Nothing essential 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?

With 0% schema description coverage, the description carries the full burden, and it succeeds. Each parameter is explained: artifact values with run_id prefix examples, model_hash as the hash of the owning model, run_id as the stable id from run history, and pinned as the desired pin state. This adds the meaning the schema omits.

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 opening sentence uses a specific verb and resource: 'Pin or unpin a saved optimizer or scenario run.' It clearly identifies the tool's action and object, making it distinguishable from generic siblings like update_run, and the artifact examples reinforce the domain.

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 implies when to use it by stating the action ('Pin or unpin'), and it notes that idempotency makes re-running safe in scripts. However, it does not explicitly contrast this tool with alternatives or give exclusion criteria, leaving usage guidance to inference.

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

Deploy Server