Skip to main content
Glama
Sign In

SimianX AI

by io.github.SimianX-AI
OverviewDiscussionsAdmin

Change a live session's models

update_live_session
Idempotent

Switch the models of a running live analysis session when the user asks; the next analysis runs on them. Their saved setup (get_settings) stays as it is.

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": {
      "session_id": "<session_id>",
      "models": "<models>"
    },
    "name": "update_live_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelsYesOnly when the user asks for specific models: agent -> model id from list_models (paid plans). Leave out to run on the user's saved setup (get_settings)
session_idYesSession id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare it is a non-destructive, idempotent, open-world write, so the safety profile is covered. The description adds genuinely useful behavior that annotations cannot express: the effect is deferred ("the next analysis runs on them") and the persisted configuration is not mutated. It omits auth/plan constraints, but the schema already flags paid plans.

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, zero filler, with the action and its immediate effect front-loaded and the non-persistence caveat second. Every clause carries information an agent needs before calling.

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?

Two required parameters, no output schema, and annotations covering safety — the description covers purpose, trigger, effect timing, and the persistence boundary, which is what an agent needs to call it correctly. Adding the paid-plan/auth caveat that lives in the schema would make it fully self-contained.

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%, so the schema already explains both parameters, including the agent-to-model-id mapping and the omit-to-use-saved-setup behavior. The description restates the models semantics without adding format, validation, or partial-update details beyond what the schema provides, making baseline 3 correct.

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?

Specific verb-plus-resource: "Switch the models of a running live analysis session," and it contrasts with the persistent counterpart by noting the saved setup (get_settings) is left untouched. That implicitly separates it from update_settings, though the distinction is left for the agent to infer rather than stated as an explicit alternative.

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?

Gives a clear trigger condition ("when the user asks" for specific models) and points at get_settings for the saved-setup case, which is the main source of confusion with this tool. It does not state an explicit when-not-to-use or mention update_settings directly, so it stops short of full routing guidance.

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

All SimianX AI 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