Skip to main content
Glama
HakashiKatake

docorbit

by HakashiKatake
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_implementation_context

Compile an evidence-grounded implementation recipe by resolving dependencies, detecting task intent, and retrieving relevant APIs within a token budget.

Instructions

High-level documentation intelligence orchestrator. Automatically resolves workspace dependencies and versions, detects task intent, retrieves relevant chunks, APIs, verified examples, and pitfalls, and compiles an evidence-grounded recipe within a strict token budget.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoOptional documentation target URL. If provided and not yet indexed in DocOrbit, DocOrbit will automatically ingest and index it before compiling context.
goalNoAlias for task.
taskNoThe specific coding task or feature to implement (e.g. "Implement Stripe webhook signature verification in Express").
queryNoAlias for task.
formatNoResponse format: "markdown" (default, human/agent-readable documentation) or "json" (structured raw machine data).
libraryNoOptional primary library or package to focus documentation on (e.g. "stripe", "next").
projectNoPath to repository workspace root for project-aware dependency detection (default: current directory).
versionNoOptional explicit target documentation version (e.g. "v14", "15.0").
tokenBudgetNoMaximum token budget for packed context (default: 4000).

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. Changed3 schema fields changedv0.1.7
    • addedInput schema / properties / goal
      Added value: +{
+  "description": "Alias for task.",
+  "type": "string"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Alias for task.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "task"
-]
  3. First observedv0.1.4

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the internal pipeline (auto dependency/version resolution, intent detection, retrieval, compilation) and the enforcement of a token budget, which is genuine behavioral context. However it omits side effects implied by the schema (auto-ingesting/indexing a URL), permission or auth needs, latency, and failure behavior, leaving significant gaps for a 9-parameter orchestrator.

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?

It is a single dense sentence with little waste, though 'High-level documentation intelligence orchestrator' is a soft, near-marketing opener. The most important outcome, the compiled recipe, lands at the end rather than being front-loaded, costing it the top mark.

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

Completeness4/5

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

With 9 optional parameters, 100% schema coverage and no output schema, the description gives an adequate account of the behavior and the nature of the result (an evidence-grounded recipe within a token budget). It does not explain how the task/goal/query aliases interact or how format selection affects output, but nothing critical for a first correct invocation 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?

Schema description coverage is 100%, so every parameter is already documented, including aliases (goal/query), format enum, and tokenBudget default. The description adds no additional meaning to any parameter. Baseline 3 is correct when the schema does all the parameter work.

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 states a specific composite verb+resource: it resolves dependencies/versions, retrieves chunks, APIs, examples and pitfalls, and compiles an evidence-grounded recipe. This distinguishes it clearly from single-purpose siblings like find_example or find_pitfall. It stops short of the 5 because it never explicitly names a sibling it replaces or differs from, though the 'orchestrator' framing implies aggregation.

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 statement of when to call this versus calling find_recipe, find_api, find_example or search_docs individually, and no prerequisites or exclusions are given. The word 'orchestrator' weakly implies an all-in-one entry point, but the agent must infer that. Comparable to the MID calibration where absent when-to-use guidance earned a 2.

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