Skip to main content
Glama
Sign In
Kanysh Basic

Kanysh Basic

by almukhanomr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

result_preview

Read-onlyIdempotent

Preview calculation or analysis reports by retrieving a PNG image and download references without loading full model arrays.

Instructions

Get report PNG (native image in MCP) and resource/download references. Does not return whole model arrays.

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": "result_preview"
  }
}

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds genuine value by disclosing the return shape (native PNG image in MCP plus resource/download references) and a scope limit (no whole model arrays). However, with no output schema it does not clarify size limits, image resolution, or what the 'resource/download references' contain.

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?

Two short sentences, front-loaded with the primary return value, with the exclusion placed after it. Slightly telegraphic phrasing ('Get report PNG (native image in MCP) and resource/download references') but no wasted text.

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 read-only tool with fully documented nested params and no output schema, the description covers the essentials (what comes back, what does not). It is still thin on the ambiguous term 'resource/download references' and gives no routing guidance against the many export/report siblings, leaving gaps an agent must resolve by guessing.

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% and the single nested parameter is fully documented in-schema (artifact id/revision, project_id with example formats). The description adds nothing beyond the schema about these fields, so the baseline 3 applies.

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 (Get) and resource (report PNG plus resource/download references), so an agent knows this returns a rendered preview rather than raw data. The exclusion 'Does not return whole model arrays' helps differentiate it from heavy data-returning siblings such as results_export, though no sibling is named explicitly.

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?

Usage is only implied: the note about not returning whole model arrays suggests 'use this when you want a lightweight visual preview instead of full data'. It never names alternatives like report_export, results_export, or artifact_inspect, nor states prerequisites such as needing an artifact id from an earlier call.

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