Skip to main content
Glama
Sign In
Kanysh Basic

Kanysh Basic

by almukhanomr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

start

Read-onlyIdempotent

Begins first-connection onboarding by guiding demo Norne setup and owner folder registration; provides instructions only, with no calculations or downloads.

Instructions

Начать / Start: first-connection onboarding, demo Norne and owner folder registration instructions. No calculation or download.

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

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

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds that this only yields instructions and performs no calculation or download. It does not disclose what the response looks like (text instructions, links, created owner folder?) or any prerequisites such as authentication or an existing project.

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?

A single front-loaded sentence that states the resource and immediately rules out calculation and download. Compact and essentially waste-free, though the mixed bilingual phrasing and the unexplained 'Norne' term slightly reduce clarity.

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 simple read-only onboarding tool with full annotation coverage and no output schema, the definition is mostly adequate, but it never says what calling it actually produces or what 'owner folder registration' means, which is the main thing an agent would need to know before invoking it.

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?

There is a single 'request' parameter that is an empty object, and the schema description coverage is 100%, so there is nothing for the description to clarify. The description adds no parameter information, but none is really needed beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names an onboarding/first-connection entry point and mentions demo 'Norne' plus owner folder registration, which hints at setup content, but it never states concretely whether the tool performs setup or merely returns instructions, and the verb 'Start' is too generic to stand alone. The 'No calculation or download' clause does usefully contrast it with the many compute/import siblings.

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?

'First-connection onboarding' implies when to call it (a new user's first step) and 'No calculation or download' implies a boundary, but no sibling is named and there is no explicit when-not guidance against candidates like project_create, diagnostics or project_list. Usage is inferred rather than 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