Skip to main content
Glama

orchestkit_install

Read-onlyIdempotent

Show how to install OrchestKit as a picker: Claude Code, Cursor or Codex, with the exact command for the picked host and a copy button. Use when a person asks how to install or set it up. Input: an optional host (claude, cursor or codex) to preselect.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "orchestkit_install"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoHost to preselect. Defaults to claude.

Output Schema

NameRequiredDescriptionDefault
hostsYes
selectedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior, that it renders a picker with a copy button and returns the exact command for the chosen host, but says nothing about prerequisites or what happens for unsupported hosts. Useful but not rich.

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, front-loaded with what the tool produces and trailing with the input. Slight redundancy between "Show how to install" and the usage sentence, but no filler.

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

Completeness5/5

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

For a single optional enum parameter with an output schema and full annotation coverage, the description supplies purpose, trigger and input summary. Nothing an agent needs in order to call it correctly is 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?

With 100% schema description coverage and an enum on host, the schema already documents the parameter fully, including the default of claude. The description restates the three allowed values and the optionality, adding essentially no semantic detail beyond the schema.

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 names a specific action and resource: render an install picker for OrchestKit across Claude Code, Cursor or Codex, returning the exact command per host. That is concrete enough to separate it from sibling doc-lookup tools, though it never explicitly names those alternatives.

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

Usage Guidelines4/5

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

It gives an explicit trigger: "Use when a person asks how to install or set it up." No when-not conditions or named alternatives are provided, so an agent could still be unsure whether to route to orchestkit_docs_search first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.