Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
logging
{}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_docsA

Search documentation chunks using hybrid FTS5 ranking, symbol awareness, and optional version filtering.

get_docA

Retrieve a specific documentation page or contextual chunk by ID or URL with complete metadata and security annotations.

find_apiA

Lookup structured OpenAPI endpoints by path, operation ID, or keyword with exact parameters, schemas, auth, and error responses.

find_exampleB

Find verified, framework-specific code examples by task, language, framework, or target API.

find_pitfallC

Search documented pitfalls, gotchas, deprecations, breaking changes, and runtime restrictions.

find_recipeA

Assemble an evidence-grounded implementation recipe with explicit prerequisites, ordered steps, and validation steps.

get_versionC

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

list_sourcesA

List all indexed documentation sources, snapshot records, doc versions, and machine-readability status.

get_implementation_contextB

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.

check_apiA

Verify agent/generated code against indexed OpenAPI schemas and documentation. Detects invalid endpoints, wrong HTTP methods, missing required parameters, deprecations, removed APIs, version syntax conflicts, and response assumptions. Distinguishes verified, warning, mismatch, and insufficient_evidence.

diff_docsA

Compare documentation snapshots and versions to detect added, removed, modified, and deprecated API endpoints, parameters, pitfalls, and content sections. Produces deterministic diffs ignoring formatting-only changes.

analyze_impactB

Compare detected documentation and API changes against current project workspace files. Identifies affected files, exact line numbers, code snippets, matched patterns, and traceable reasons with certainty rankings (high, medium, heuristic).

get_documentation_mapA

Retrieve the hierarchical documentation map, page tree, section headings, and estimated token budget footprints for indexed documentation.

export_agent_contextA

Deterministically generate and export agent-native documentation context files (AGENTS.md, CLAUDE.md, skill.md, llms.txt, docs-map.md) grounded in project dependency versions and authoritative documentation.

ingest_docA

Ingest, crawl, parse, and index authoritative documentation from any URL or raw content directly into DocOrbit. Extracts semantic chunks, OpenAPI endpoints, code examples, and pitfalls. If taskContext is provided, immediately synthesizes and returns an evidence-grounded implementation recipe with exact code and API details.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Indexed Documentation SourcesCollection of all indexed documentation sources, version status, and snapshots.

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