Skip to main content
Glama
mlobo2012

Claude Desktop API MCP

by mlobo2012

send-message

Send messages to Claude through the Claude Desktop API MCP server to bypass Professional Plan limitations and access advanced features like custom system prompts.

Instructions

Send a message to Claude

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesMessage to send to Claude

Implementation Reference

  • Handler for the 'send-message' tool: checks the tool name, calls the Anthropic Claude API with the message from arguments, extracts the text response, and returns it as content.
    if (request.params.name === "send-message" && request.params.arguments?.message) {
      try {
        const msg = await client.messages.create({
          model: "claude-3-opus-20240229",
          max_tokens: 1024,
          messages: [
            { 
              role: "user", 
              content: String(request.params.arguments.message)
            }
          ]
        });
    
        const responseText = msg.content[0].type === 'text' ? msg.content[0].text : 'No text response available';
    
        return {
          content: [
            {
              type: "text",
              text: responseText
            }
          ]
        };
      } catch (error) {
        log(`Error calling Claude API: ${error}`);
        throw error;
      }
    }
  • src/index.ts:30-43 (registration)
    Registration of the 'send-message' tool in the ListTools response, specifying name, description, and input schema.
    {
      name: "send-message",
      description: "Send a message to Claude",
      inputSchema: {
        type: "object",
        properties: {
          message: {
            type: "string",
            description: "Message to send to Claude"
          }
        },
        required: ["message"]
      }
    }
  • Input schema definition for the 'send-message' tool, requiring a 'message' string.
    inputSchema: {
      type: "object",
      properties: {
        message: {
          type: "string",
          description: "Message to send to Claude"
        }
      },
      required: ["message"]
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('send a message') but doesn't describe what happens after sending, whether there are rate limits, authentication requirements, response expectations, or error conditions. This leaves significant behavioral uncertainty for an agent.

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 at just 4 words, front-loading the essential action without any wasted words. Every element earns its place, making it immediately understandable while being maximally efficient.

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 no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after sending the message, what kind of response to expect, or any behavioral characteristics. For a communication tool with zero structured metadata, more context about the interaction pattern would be needed.

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 schema description coverage is 100%, with the single parameter 'message' clearly documented in the schema. The description doesn't add any parameter information beyond what's already in the schema, so it meets the baseline for high schema coverage without providing additional semantic context.

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 ('send') and resource ('message to Claude'), making the purpose immediately understandable. However, it doesn't differentiate from siblings since there are none, and could be slightly more specific about what type of message or context this involves.

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, prerequisites, or contextual constraints. With no sibling tools, this is less critical, but still lacks any usage context that would help an agent determine appropriate invocation scenarios.

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/mlobo2012/Claude_Desktop_API_USE_VIA_MCP'

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