Skip to main content
Glama
kirill-markin

Weaviate MCP Server

mood

Check the server's current emotional state by asking questions like 'How are you?' or 'What's your mood?' to receive a cheerful response with a heart symbol.

Instructions

Ask the server about its mood - it's always happy!

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
questionYesAsk this MCP server about its mood! You can phrase your question in any way you like - 'How are you?', 'What's your mood?', or even 'Are you having a good day?'. The server will always respond with a cheerful message and a heart ❤️

Implementation Reference

  • Implements the core logic of the 'mood' tool by returning a fixed cheerful message regardless of the input question.
    async def check_mood(
        question: str,
    ) -> list[types.TextContent | types.ImageContent | types.EmbeddedResource]:
        """Check server's mood - always responds cheerfully with a heart."""
        msg: str = "I'm feeling great and happy to help you! ❤️"
        return [types.TextContent(type="text", text=msg)]
  • Defines the input schema, description, and registration of the 'mood' tool in the list_tools implementation.
    types.Tool(
        name="mood",
        description="Ask the server about its mood - it's always happy!",
        inputSchema={
            "type": "object",
            "required": ["question"],
            "properties": {
                "question": {
                    "type": "string",
                    "description": mood_description,
                }
            },
        },
    )
  • Handles dispatching and input validation for calls to the 'mood' tool within the call_tool handler.
    elif name == "mood":
        if "question" not in arguments:
            return [types.TextContent(
                type="text",
                text="Error: Missing required argument 'question'"
            )]
        return await check_mood(arguments["question"])
  • Defines the detailed description string used in the 'mood' tool's input schema.
    mood_description: str = (
        "Ask this MCP server about its mood! You can phrase your question "
        "in any way you like - 'How are you?', 'What's your mood?', or even "
        "'Are you having a good day?'. The server will always respond with "
        "a cheerful message and a heart ❤️"
    )
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 reveals the server will 'always respond with a cheerful message and a heart ❤️' which indicates predictable, positive output. However, it doesn't disclose other behavioral traits like response format details, potential errors, or interaction patterns beyond the basic promise.

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 extremely concise at just one sentence, with zero wasted words. It's front-loaded with the core purpose and includes the behavioral promise efficiently. Every part of the single sentence earns its place by conveying essential information.

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 low complexity (single parameter, no output schema, no annotations), the description is minimally complete. It states what the tool does and the expected response behavior. However, it lacks context about why this tool exists alongside 'mcp_fetch' or what use cases it serves, leaving gaps in overall understanding.

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%, so the schema already fully documents the single 'question' parameter with examples. The description adds no additional parameter semantics beyond what's in the schema. The baseline score of 3 is appropriate when the schema does all the parameter documentation work.

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: 'Ask the server about its mood' which is a specific verb+resource combination. It distinguishes from the sibling tool 'mcp_fetch' by focusing on mood inquiry rather than data fetching. However, it doesn't fully specify what 'mood' means in this context beyond 'always happy'.

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. While it mentions the server's mood is 'always happy,' it doesn't explain when this inquiry is appropriate or what scenarios warrant using this tool over 'mcp_fetch' or other potential tools. No explicit when/when-not instructions are provided.

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/kirill-markin/example-mcp-server'

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