ADK MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_adkB | Search the Google ADK documentation for relevant information. Args: query: The search query. language: The programming language to filter by ("python", "go", "java", or "all"). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clear and distinct, so disambiguation is not a concern.
The tool name 'search_adk' follows a clear verb_noun pattern, and with only one tool there are no inconsistencies. The naming is predictable and appropriate.
A single tool is on the borderline of being too thin, but for a documentation search server, it may be sufficient. However, it feels limited compared to typical MCP servers with a broader toolset.
The search tool covers the primary need of querying ADK documentation with language filtering. However, it lacks tools for retrieving full document content or browsing available topics, which are minor gaps.