F
licenseNot graded
qualityD
maintenanceEnables AI agents to search and retrieve Holochain documentation, including developer guides, HDK functions, and HDI API references.
2
developer-toolkit-mcp
Server Details
The documentation, as a tool your agent can call: 950+ AI-dev guides. Search + fetch tools.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- mjaskolski/developer-toolkit-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.1/5.0
Tool DescriptionsA
Average 4.3/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation5/5
The two tools have completely distinct purposes: search queries the documentation index, while fetch retrieves a specific article by ID. There is no overlap or ambiguity between them.
Naming Consistency4/5
Both tool names are single lowercase verbs ('search', 'fetch'), which is consistent in style. However, they lack a noun prefix (e.g., 'search_docs', 'fetch_article'), but the pattern is uniform and predictable.
Tool Count3/5
With only 2 tools, the set feels minimal but is perfectly scoped for a documentation search-and-retrieve utility. It's on the low end of acceptable, but the narrow purpose justifies the small count.
Completeness4/5
The search-fetch pair covers the core workflow for documentation lookup. A 'list' or 'browse' tool could be useful, but for a search-driven retrieval server, these two tools satisfy the primary use case without major gaps.
Available Tools
2 toolsfetchFetch a documentation articleARead-onlyInspect
Retrieve the complete markdown of one documentation article by the id returned from search (for example en/claude-code/advanced-techniques/hooks-automation).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Article id from a `search` result. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| id | Yes | |
| url | Yes | |
| text | Yes | |
| title | Yes | |
| metadata | Yes |
Tool Definition Quality
A4.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds that the output is markdown and the id source, but doesn't disclose additional behavioral traits such as pagination or error handling. Since annotations carry the main transparency load, the added value is modest.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that directly states the action and the parameter source. Every word earns its place with no redundancy or 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?
The tool is simple with one parameter, read-only annotations, and an output schema. The description covers the essential workflow (use id from search), and the output schema handles return values, so no additional information is needed for completeness.
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%, and the schema already describes `id` as 'Article id from a `search` result.' The description repeats the same information without adding new meaning, so it doesn't compensate beyond the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly specifies the verb 'Retrieve' and the resource 'complete markdown of one documentation article', and it explicitly mentions the id comes from `search`, distinguishing it from the sibling tool. The purpose is unmistakable.
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?
The description states that the id must come from a `search` result, which implies usage after search. It provides clear context on how to retrieve the id, but it doesn't explicitly mention when not to use this tool or name alternatives beyond the implied `search` workflow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
searchSearch the documentationARead-onlyInspect
Search the AI Developer Toolkit documentation: 950+ guides on Cursor, Claude Code and OpenAI Codex, covering setup, agent workflows, hooks, MCP, testing, CI and deployment, in English and Polish. Returns ranked results; pass a result id to fetch for the full text.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Natural-language query or keywords. Polish queries return Polish articles. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| results | Yes |
Tool Definition Quality
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark the tool as read-only and closed-world. The description adds extra context about returning ranked results and the bilingual (English/Polish) nature, which goes beyond the annotations. This is useful but not over-elaborated, so a 4 is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loads the tool's purpose and scope, and wastes no words. It efficiently communicates all needed information without redundancy.
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?
With a clear scope, ranked results, language coverage, and a pointer to the sibling tool for full text, combined with read-only annotations and an output schema, the description is complete. There is no missing behavioral or workflow context for this simple tool.
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?
The schema description already fully covers the `query` parameter (100% coverage), and the description does not add further parameter-specific meaning. The description mentions Polish and English, but that overlaps with schema information about Polish queries, so the added value is minimal.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as a search over the AI Developer Toolkit documentation, specifies the covered topics and languages, and distinguishes itself from the sibling tool `fetch` by stating that full text is retrieved via a result id.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly states the workflow: 'pass a result id to fetch for the full text' – indicating when to use fetch and that search is for initial ranked results. This provides clear alternative usage for full text retrieval.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- FlicenseAqualityDmaintenanceProvides AI models with direct access to documentation for over 600 technologies from DevDocs.io, including popular languages, frameworks, and tools. It enables comprehensive searching, content retrieval, and offline access via an intelligent local caching system.122
- AlicenseNot gradedqualityDmaintenanceOn-device documentation search for agents54MIT
- AlicenseNot gradedqualityCmaintenanceProvides real-time, up-to-date documentation for major LLM providers (OpenAI, Anthropic, Google Gemini) to prevent hallucinations and outdated code patterns in AI agents.106MIT