Skip to main content
Glama
Sign In
Kanysh Basic

Kanysh Basic

by almukhanomr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

scene_show

Persist artifact visibility, opacity, property, selection, stride, and seismic slice options in the unified scene; TWT overlays need explicit velocity and origin. Does not start a viewer job.

Instructions

Persist artifact visibility, opacity, property, selection, stride and seismic slice options in the unified scene. TWT overlay needs explicit velocity and origin. Does not start a viewer job.

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

Input Schema

NameRequiredDescriptionDefault
requestYesTool arguments object (all fields documented; Z is positive upward).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only cover the safety profile (not read-only, not destructive, not idempotent); the description adds real behavioral context beyond them by clarifying that this only records scene state and launches no viewer job, plus the TWT velocity/origin requirement. It still omits whether scene entries are replaced or merged and how long the persisted state survives.

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?

Three short sentences with the core purpose front-loaded and no filler. The opening enumeration of six state fields is slightly list-dumpy but is also the most information-dense part, so nothing is wasted.

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

Completeness3/5

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

For a mutation tool with no output schema, the description never says what is returned (a scene entry, a job handle, or nothing) – notable given the schema's idempotency_key talk of 'returning the existing job'. It covers the core intent and one precondition but leaves the response contract and scene-mutation semantics unspecified.

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 baseline is 3, but the description earns extra credit by stating a cross-parameter dependency the schema documents only field-by-field: TWT overlay requires both velocity_m_s and origin_z_m to be supplied. That is genuine added meaning an agent cannot infer from isolated field descriptions.

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?

States a specific verb ('persist') and resource ('the unified scene') plus the exact state it controls (visibility, opacity, property, selection, stride, seismic slice options), which distinguishes it from read-only siblings such as scene_inspect. It does not name a sibling alternative explicitly, so it stops short of a 5.

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?

Adds one useful negative scope statement ('does not start a viewer job') and a precondition for TWT overlay (explicit velocity and origin), implying when the tool is appropriate. However, it never says when to use this versus scene_inspect, scene_export, or seismic_slice, leaving the routing decision 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

Other Tools