Skip to main content
Glama
t0ster
by t0ster

get_meme_info

Retrieve details about meme templates and their text placeholder requirements to prepare content for meme generation.

Instructions

Get information about available memes and their text placeholder requirements.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meme_nameNoOptional: Get info for a specific meme

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_meme_info' tool. It is decorated with @mcp.tool() which also serves as its registration. The function retrieves meme configurations using get_meme_configs() and returns detailed information about a specific meme (if provided) or lists all available memes with their placeholders.
    @mcp.tool()
    async def get_meme_info(
        meme_name: Annotated[
            str | None, Field(description="Optional: Get info for a specific meme")
        ] = None,
    ) -> dict:
        """Get information about available memes and their text placeholder requirements."""
        meme_configs = get_meme_configs()
        if meme_name:
            if meme_name not in meme_configs:
                return {"status": "error", "message": f"Unknown meme type: {meme_name}"}
    
            config = meme_configs[meme_name]
            placeholder_names = list(config.placeholders.keys())
            return {
                "status": "success",
                "meme_name": meme_name,
                "template_file": config.template_file,
                "placeholder_names": placeholder_names,
                "example_usage": {
                    "meme_name": meme_name,
                    "texts": {name: f"Example {name}" for name in placeholder_names},
                },
            }
        else:
            all_memes = {}
            for meme_type, config in meme_configs.items():
                all_memes[meme_type] = {
                    "placeholder_names": list(config.placeholders.keys()),
                    "template_file": config.template_file,
                }
    
            return {
                "status": "success",
                "available_memes": all_memes,
                "total_memes": len(all_memes),
            }
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. While it indicates this is a read operation ('Get information'), it doesn't address important behavioral aspects like whether this requires authentication, rate limits, pagination for multiple memes, error conditions, or what happens when meme_name is null. The description is minimal and leaves significant behavioral questions unanswered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence that efficiently communicates the core purpose. There's no wasted language or unnecessary elaboration. However, it could be slightly more front-loaded by explicitly stating this is for retrieving metadata rather than generating content, which would better distinguish it from the sibling tool.

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 that there's an output schema (which handles return values), a single optional parameter with full schema coverage, and no annotations, the description is minimally adequate. However, for a tool that presumably returns structured information about memes (including their text placeholder requirements), the description could better explain the scope of information returned and how it relates to the sibling 'generate_meme' 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 input schema has 100% description coverage, with the single parameter 'meme_name' documented as 'Optional: Get info for a specific meme'. The description adds no additional parameter semantics beyond what's already in the schema. It mentions 'text placeholder requirements' which relates to output rather than input parameters. With complete schema coverage, the baseline score of 3 is appropriate.

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: 'Get information about available memes and their text placeholder requirements.' It specifies the verb ('Get information') and resource ('memes'), and mentions the type of information returned (text placeholder requirements). However, it doesn't explicitly differentiate from its sibling tool 'generate_meme' beyond the general 'get info' vs 'generate' distinction.

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 its sibling 'generate_meme'. It doesn't mention prerequisites, alternative approaches, or contextual factors that would help an agent decide between retrieving meme information versus generating a meme. The only implied usage is when information about memes is needed, but this is too vague for effective tool selection.

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/t0ster/meme-generator-mcp'

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