Skip to main content
Glama
meilisearch

Meilisearch MCP Server

Official
by meilisearch

update-connection-settings

Modify Meilisearch connection settings, including URL and API key, to ensure proper integration with LLM interfaces via the MCP server.

Instructions

Update Meilisearch connection settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNo
urlNo

Implementation Reference

  • Handler logic in the call_tool method that matches the tool name and calls update_connection with arguments, then returns success message.
    elif name == "update-connection-settings":
        self.update_connection(
            arguments.get("url"), arguments.get("api_key")
        )
        return [
            types.TextContent(
                type="text",
                text=f"Successfully updated connection settings to URL: {self.url}",
            )
        ]
  • Tool registration in list_tools decorator, including name, description, and input schema definition.
    types.Tool(
        name="update-connection-settings",
        description="Update Meilisearch connection settings",
        inputSchema={
            "type": "object",
            "properties": {
                "url": {"type": "string"},
                "api_key": {"type": "string"},
            },
            "additionalProperties": False,
        },
    ),
  • Helper method that performs the actual connection update by setting new URL/API key and reinitializing MeilisearchClient and ChatManager.
    def update_connection(
        self, url: Optional[str] = None, api_key: Optional[str] = None
    ):
        """Update connection settings and reinitialize client if needed"""
        if url:
            self.url = url
        if api_key:
            self.api_key = api_key
    
        self.meili_client = MeilisearchClient(self.url, self.api_key)
        self.chat_manager = ChatManager(self.meili_client.client)
        self.logger.info("Updated Meilisearch connection settings", url=self.url)
Behavior2/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 states 'Update' which implies a mutation operation, but doesn't clarify whether this requires specific permissions, if changes are reversible, what happens to existing settings not mentioned, or any rate limits. This is a significant gap for a mutation tool with zero annotation coverage.

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, efficient sentence with zero wasted words. It's appropriately sized for a simple update operation and front-loads the essential information, making it easy to parse quickly.

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 this is a mutation tool with no annotations, 0% schema description coverage, and no output schema, the description is inadequate. It should explain more about what connection settings are, what the update affects, potential side effects, and expected outcomes to help the agent use it correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'connection settings' which hints at the purpose of 'api_key' and 'url' parameters, but doesn't explain what these settings control, their expected formats, or whether both are required. The description adds minimal value beyond what can be inferred from parameter names.

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 verb 'Update' and the resource 'Meilisearch connection settings', making the tool's purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'get-connection-settings' or explain what specific connection settings are being updated beyond what the parameters suggest.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'get-connection-settings' for retrieval or other update tools. There's no mention of prerequisites, typical use cases, or when not to use it, leaving the agent with minimal context for decision-making.

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

Related 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/meilisearch/meilisearch-mcp'

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