Skip to main content
Glama
HakashiKatake

docorbit

by HakashiKatake
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_version

Resolve the exact compatible documentation version for a library by inspecting workspace dependencies through the SemVer confidence ladder.

Instructions

Inspect workspace dependencies and resolve the exact compatible documentation version using the SemVer confidence ladder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoResponse format: "markdown" (default, human/agent-readable documentation) or "json" (structured raw machine data).
libraryYesPackage or library name to check (e.g. "next", "stripe", "fastapi").
projectPathNoWorkspace root directory containing package manifests (default: current directory).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.3
    • addedInput schema / properties / format
      Added value: +{
+  "description": "Response format: \"markdown\" (default, human/agent-readable documentation) or \"json\" (structured raw machine data).",
+  "enum": [
+    "markdown",
+    "json"
+  ],
+  "type": "string"
+}
  2. First observedv0.1.4

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it. It never states whether it reads package manifests only or touches the network, whether it is side-effect free, or what the 'confidence ladder' returns or how to interpret it. The mysterious 'SemVer confidence ladder' concept is introduced without explanation.

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 with no padding. It is efficient, though the undefined 'confidence ladder' term costs a little clarity for the space it occupies.

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

Completeness2/5

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

No annotations and no output schema, so the description must explain what resolution actually produces — and it does not. For a three-parameter tool whose whole value is a resolved version plus some notion of confidence, the return semantics and any failure behavior are 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 description coverage is 100%, so format, library and projectPath are fully documented in the schema, establishing the baseline of 3. The description's mention of 'workspace dependencies' loosely ties to projectPath but adds no syntax, defaults, or format guidance 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?

States a specific verb and resource: inspect workspace dependencies and resolve a compatible documentation version. This is distinguishable from the sibling retrieval tools (search_docs, get_doc), though the phrase 'SemVer confidence ladder' is unexplained jargon and the description never names which sibling it complements.

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?

There is no explicit statement of when to call this versus alternatives such as get_documentation_map or search_docs. The 'inspect workspace dependencies' phrasing weakly implies a pre-step before fetching docs, but no when/when-not condition or ordering guidance is given.

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