Skip to main content
Glama
gemini2026

Documentation Search MCP Server

by gemini2026

get_current_config

View the active configuration to use as a template for customizing documentation search settings.

Instructions

Returns the current, active configuration of the MCP server. This allows users to view the default config and use it as a template for local overrides.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_current_config' tool. It returns the global 'config' dictionary which holds the active MCP server configuration loaded at startup.
    async def get_current_config():
        """
        Returns the current, active configuration of the MCP server.
        This allows users to view the default config and use it as a template for local overrides.
        """
        try:
            # The `config` global is a dictionary created from the Pydantic model
            # at startup, so it represents the active configuration.
            return config
        except Exception as e:
            return {"error": f"Could not retrieve configuration: {str(e)}"}
  • The @mcp.tool() decorator registers the get_current_config function as an MCP tool.
    async def get_current_config():
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates this is a read-only operation ('Returns') and implies it provides a default configuration view, but doesn't detail potential side effects, authentication needs, rate limits, or error conditions. The description adds basic context but lacks comprehensive behavioral traits.

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 perfectly concise with two sentences that directly address purpose and utility. The first sentence states what the tool does, and the second explains its practical value. There's no wasted language or redundancy.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is adequate but minimal. It explains what the tool returns but doesn't describe the format or structure of the configuration data, which would be helpful for an agent to understand the return value. The description is complete enough for basic understanding but lacks depth.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose. This meets the baseline of 4 for zero-parameter tools.

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 the tool's purpose with a specific verb ('Returns') and resource ('current, active configuration of the MCP server'). It distinguishes from siblings by focusing on configuration retrieval rather than operations like scanning or searching. However, it doesn't explicitly differentiate from the similar 'get_environment_config' sibling tool.

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 provides implied usage guidance by mentioning 'use it as a template for local overrides,' suggesting when this tool might be helpful. However, it lacks explicit guidance on when to use this versus alternatives like 'get_environment_config' or other configuration-related tools, and doesn't specify prerequisites or exclusions.

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/gemini2026/documentation-search-mcp'

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