Skip to main content
Glama
Sign In
Kanysh Basic

Kanysh Basic

by almukhanomr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

scene_export

Export a persisted scene as interactive PyVista/trame HTML, PNG, and scene.json via an isolated worker; use bounded previews and explicit stride/cell_range for large grids, returning a job_id.

Instructions

Publish persisted scene as interactive PyVista/trame HTML, PNG and scene.json in an isolated worker. Bounded preview; explicit stride/cell_range for large grids. Returns job_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": {
      "request": "<request>"
    },
    "name": "scene_export"
  }
}

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.5/5.0
Behavior4/5

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

The annotations already state readOnly=false, destructive=false, and idempotent=false; the description usefully adds that work runs in an isolated worker, that large grids are preview-bounded, and that the call returns a job_id rather than the final artifacts synchronously. It leaves artifact locations/retention and any permission requirements unstated, but it adds meaningful behavioral context beyond the annotations.

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 two dense, front-loaded sentences that state the core operation, output formats, isolation model, and return value. There is no filler, though the stride/cell_range phrase is factually mismatched with the schema.

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 nested export/job tool with no output schema, the description states only that it returns job_id and does not explain artifact retrieval, output locations, or the job_status polling flow. It covers purpose, formats, and isolation sufficiently to start using the tool, but operational completeness has clear gaps.

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

Parameters2/5

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

The schema has 100% description coverage and documents the actual controls such as max_cells, max_points, execution, and idempotency_key. The description instead mentions 'explicit stride/cell_range for large grids,' but no stride or cell_range properties exist in the schema, which is misleading rather than additive parameter guidance.

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?

The description states a specific verb and resource: publish a persisted scene, and it enumerates concrete output formats (interactive PyVista/trame HTML, PNG, scene.json) plus the isolated-worker execution context. It does not explicitly differentiate from siblings such as scene_show or scene_inspect, though export versus show/inspect is reasonably inferable.

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?

It implies the tool is for bounded previews and for large grids needing stride/cell_range control, but it gives no explicit when-not guidance or named alternative. It also does not tell the agent to poll job_status after receiving job_id.

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