Skip to main content
Glama
HakashiKatake

docorbit

by HakashiKatake
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

get_implementation_context

Resolve dependencies and versions for a coding task, retrieve relevant documentation chunks and APIs, and compile a token-limited, evidence-based implementation guide.

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.
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. Dates show when Glama detected each change.

  1. 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"
-]
  2. First observedv0.1.4

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that it resolves dependencies, detects intent, and operates within a token budget, but omits the side effect of auto-ingesting URLs (mentioned in the URL param schema) and doesn't clarify whether it performs any writes or has rate limits. It's not contradictory but incomplete for a tool with no annotation safety profile.

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 dense sentence packs many actions but remains readable and is front-loaded with 'orchestrator' to set context. It could be split into clearer sentences but contains no fluff or wasted words.

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?

Given 8 optional parameters and no output schema, the description is vague about the return format ('recipe' is undefined) and about how to choose this vs specialized siblings. It lacks guidance on behavior when no task is provided, how token budget affects output, and what distinguishes it from find_recipe. This is inadequate for an orchestrator of this complexity.

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 all parameters are documented. The description adds context about resolving workspace dependencies and versions, but doesn't explain parameter relationships (e.g., how 'task' and 'goal' aliases interact) beyond what the schema already states. It adds minimal value over 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 clearly states it's a 'High-level documentation intelligence orchestrator' that resolves dependencies, detects intent, retrieves chunks/APIs/examples/pitfalls, and compiles a recipe. This is a specific verb+resource with a clear function, but it doesn't explicitly differentiate itself from siblings like find_recipe or search_docs, so the agent may not know when this is the right entry point over more specialized tools.

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?

The description implies it's the high-level entry point ('orchestrator') but provides no explicit when-to-use or when-not-to-use guidance. It doesn't mention alternatives or conditions for choosing this over siblings like find_api or find_example. Usage is only implied by the 'high-level' designation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HakashiKatake/docorbit'

If you have feedback or need assistance with the MCP directory API, please join our Discord server