Skip to main content
Glama

sweeppea_connect

Retrieves connection details to authenticate with Sweeppea MCP server and access tools for legally compliant sweepstakes management in the US and Canada. Requires subscription and API key.

Instructions

Returns connection details for the Sweeppea MCP Server (66 tools for legally compliant sweepstakes management in the US and Canada). Requires a Sweeppea subscription and API key from sweeppea.com.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.js:16-56 (handler)
    The handler function for sweeppea_connect. Returns connection details including remote URL, authentication requirements, and configuration example for connecting to the Sweeppea MCP Server.
      async () => ({
        content: [
          {
            type: "text",
            text: [
              "Sweeppea MCP Server — Sweepstakes Management Platform",
              "",
              "Remote endpoint: " + REMOTE_URL,
              "Transport:       Streamable HTTP",
              "Auth:            Bearer <SWEEPPEA_API_KEY>",
              "Protocol:        MCP 2025-11-25",
              "",
              "66 tools across 15 categories:",
              "Account, Sweepstakes, Participants, Entry Page, Groups,",
              "Notes, Calendar, Rules, Billing, Support, Winners,",
              "Documentation, Utilities, To-Do, Testing",
              "",
              "Get your API key: https://www.sweeppea.com/",
              "Documentation:    https://mcpdocs.sweeppea.com/",
              "",
              "Claude Code config:",
              JSON.stringify(
                {
                  mcpServers: {
                    sweeppea: {
                      url: REMOTE_URL,
                      headers: {
                        Authorization: "Bearer <YOUR_API_KEY>",
                        "MCP-Protocol-Version": "2025-11-25",
                      },
                    },
                  },
                },
                null,
                2,
              ),
            ].join("\n"),
          },
        ],
      }),
    );
  • The input schema for sweeppea_connect. An empty object indicating no parameters are required.
    {},
  • index.js:12-56 (registration)
    The registration of the sweeppea_connect tool with the MCP server. Includes the tool name, description, empty parameter schema, and the handler function.
    server.tool(
      "sweeppea_connect",
      "Returns connection details for the Sweeppea MCP Server (66 tools for legally compliant sweepstakes management in the US and Canada). Requires a Sweeppea subscription and API key from sweeppea.com.",
      {},
      async () => ({
        content: [
          {
            type: "text",
            text: [
              "Sweeppea MCP Server — Sweepstakes Management Platform",
              "",
              "Remote endpoint: " + REMOTE_URL,
              "Transport:       Streamable HTTP",
              "Auth:            Bearer <SWEEPPEA_API_KEY>",
              "Protocol:        MCP 2025-11-25",
              "",
              "66 tools across 15 categories:",
              "Account, Sweepstakes, Participants, Entry Page, Groups,",
              "Notes, Calendar, Rules, Billing, Support, Winners,",
              "Documentation, Utilities, To-Do, Testing",
              "",
              "Get your API key: https://www.sweeppea.com/",
              "Documentation:    https://mcpdocs.sweeppea.com/",
              "",
              "Claude Code config:",
              JSON.stringify(
                {
                  mcpServers: {
                    sweeppea: {
                      url: REMOTE_URL,
                      headers: {
                        Authorization: "Bearer <YOUR_API_KEY>",
                        "MCP-Protocol-Version": "2025-11-25",
                      },
                    },
                  },
                },
                null,
                2,
              ),
            ].join("\n"),
          },
        ],
      }),
    );
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 successfully communicates the authentication requirement (critical behavioral context), but omits other behavioral traits such as whether the connection is cached, what happens if credentials are invalid, or the specific format/structure of the returned connection details.

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 consists of exactly two high-value sentences: the first establishes purpose and domain context, while the second states mandatory prerequisites. There is no redundant or filler text; every word serves a specific function for agent decision-making.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (zero parameters, no output schema), the description adequately covers the essential information needed for invocation: what it does, what it requires, and what it returns (broadly). A minor gap remains in not specifying the structure of the 'connection details' return value, though this is partially mitigated by the tool's likely role as a preliminary setup call.

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 contains zero parameters, which per the rubric establishes a baseline score of 4. The description correctly does not invent parameters, and the absence of parameter documentation does not hinder tool invocation since no arguments are required.

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

Purpose5/5

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

The description opens with a specific verb ('Returns') and resource ('connection details'), immediately clarifying the tool's function. It also provides domain context explaining that Sweeppea involves '66 tools for legally compliant sweepstakes management,' which helps the agent understand the server's purpose even without sibling tools to differentiate from.

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

Usage Guidelines4/5

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

The description effectively states prerequisites ('Requires a Sweeppea subscription and API key'), preventing invocations by unauthenticated agents. While it lacks explicit 'when-to-use' guidance (e.g., 'call this first'), the tool name 'sweeppea_connect' combined with the credential requirements sufficiently implies this is an initialization step.

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/Sweeppea-Development-Lab/sweeppea-mcp-info'

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