Skip to main content
Glama
Sign In
Kanysh Basic

Kanysh Basic

by almukhanomr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

results_export

Export immutable analysis and calculation reports to XLSX and PDF, with per-value workbook checks and PDF provenance/status text so NOT RUN or FAIL statuses stay visible.

Instructions

Export immutable analysis/calculation reports to XLSX (scenario/region sheets) and PDF (tables, assumptions, source tornado/S-curve plots). Independently checks every workbook value and PDF provenance/status text. Source NOT RUN/FAIL remains visible; export PASS is serialization only. Explicit PDF table row limit; full tables in XLSX/JSON.

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": "results_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?

Adds meaningful behavior beyond the annotations: independent workbook/PDF validation, preservation of source NOT RUN/FAIL status, clarification that export PASS is only serialization, and a PDF row limit. It still does not explain side effects such as where files are written, return behavior, or idempotency-key handling.

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?

Four dense sentences, front-loaded with the core export action and formats, with no wasted text. The status and validation caveats are concise and useful.

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?

Covers output formats, validation behavior, status semantics, and PDF limits for a complex export tool. However, with no output schema and a nested request object, it omits what the tool returns, file locations, and execution/async behavior, leaving important context missing.

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 coverage is 100%, so the nested request fields are already documented. The description reinforces formats and the PDF row limit, but adds little parameter meaning beyond what the schema already provides.

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 (Export) and resource (immutable analysis/calculation reports) with concrete output formats and sheet/plot contents. It is clear, but it does not differentiate itself from the sibling report_export tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool does but gives no explicit guidance on when to use it instead of report_export or result_preview, and no prerequisites or exclusions are stated.

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