Skip to main content
Glama
0x8687

Meme MCP Server

by 0x8687

get-gmail-settings

Retrieve Gmail configuration settings for integration with meme generation workflows in the Meme MCP Server.

Instructions

Get Gmail settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The inline handler function for the 'get-gmail-settings' MCP tool. It uses the VercelAIToolSet (Composio integration) to execute the 'GMAIL_GET_SETTINGS' action, retrieves the settings, and formats them as a JSON string in the tool response. Includes error handling and success/failure responses.
    server.tool("get-gmail-settings", "Get Gmail settings", {}, async (args, extra) => {
        try {
            const userAddress = "default-user";
            
            const result = await toolset.executeAction({
                action: "GMAIL_GET_SETTINGS",
                entityId: userAddress,
                params: {}
            });
            
            if (result.successful) {
                const settings = result.data?.response_data as any;
                return {
                    content: [{ 
                        type: "text", 
                        text: `⚙️ Gmail Settings:\n\n${JSON.stringify(settings, null, 2)}` 
                    }],
                };
            } else {
                return {
                    content: [{ 
                        type: "text", 
                        text: `❌ Failed to get Gmail settings: ${result.error || 'Unknown error'}` 
                    }],
                };
            }
        } catch (error) {
            console.error('Error getting Gmail settings:', error);
            return {
                content: [{ 
                    type: "text", 
                    text: `Error getting Gmail settings: ${error instanceof Error ? error.message : String(error)}` 
                }],
            };
        }
    });
  • src/tools.ts:648-683 (registration)
    Registration of the 'get-gmail-settings' tool using server.tool() within the registerTools function. Uses an empty schema object ({}) indicating no input parameters are required.
    server.tool("get-gmail-settings", "Get Gmail settings", {}, async (args, extra) => {
        try {
            const userAddress = "default-user";
            
            const result = await toolset.executeAction({
                action: "GMAIL_GET_SETTINGS",
                entityId: userAddress,
                params: {}
            });
            
            if (result.successful) {
                const settings = result.data?.response_data as any;
                return {
                    content: [{ 
                        type: "text", 
                        text: `⚙️ Gmail Settings:\n\n${JSON.stringify(settings, null, 2)}` 
                    }],
                };
            } else {
                return {
                    content: [{ 
                        type: "text", 
                        text: `❌ Failed to get Gmail settings: ${result.error || 'Unknown error'}` 
                    }],
                };
            }
        } catch (error) {
            console.error('Error getting Gmail settings:', error);
            return {
                content: [{ 
                    type: "text", 
                    text: `Error getting Gmail settings: ${error instanceof Error ? error.message : String(error)}` 
                }],
            };
        }
    });
  • Empty schema ({}) for the 'get-gmail-settings' tool, specifying no input validation or parameters.
    server.tool("get-gmail-settings", "Get Gmail settings", {}, async (args, extra) => {
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 but only states the action ('Get') without detailing traits like read-only status, authentication needs, rate limits, or response format. It lacks critical context for safe and effective use.

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

Conciseness3/5

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

The description is concise with a single sentence, but it's under-specified rather than efficiently informative. It lacks front-loaded details that would help an agent, making it more of a placeholder than a well-structured explanation.

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 the complexity of a settings retrieval tool with no annotations and no output schema, the description is incomplete. It doesn't explain what settings are returned, potential errors, or behavioral aspects, leaving significant gaps for the agent to infer.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is appropriate here, earning a baseline score above 3 due to the absence of parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get Gmail settings' is a tautology that essentially restates the tool name 'get-gmail-settings' without adding meaningful specificity. It doesn't clarify what specific settings are retrieved or how this differs from other Gmail-related tools like 'get-email' or 'get-labels', which would be needed for sibling differentiation.

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

Usage Guidelines1/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. It doesn't mention context, prerequisites, or exclusions, such as whether it requires authentication or if it's for retrieving global versus user-specific settings, leaving the agent with no usage direction.

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/0x8687/mcp-gmail-v1'

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