Skip to main content
Glama
carlosazaustre

Activity Reporting MCP Server

submit_workshop

Submit workshop activity details including title, description, date, attendees, format, and country to the Activity Reporting MCP Server for accurate record-keeping and reporting.

Instructions

Submit a workshop activity draft

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activityDateYesDate of your workshop (YYYY-MM-DD format)
activityUrlYesWorkshop/event link
additionalInfoNoAdditional information (optional)
countryNoCountry (required if eventFormat is In-Person or Hybrid)
descriptionYesWhat was it about?
eventFormatYesSelect event format
inPersonAttendeesNoIn-person attendees (required if eventFormat is Hybrid or In-Person)
metricsYes
privateNoDo you want to make this activity private? (optional)
tagsNoTags (optional)
titleYesWhat was the name of your workshop session?

Implementation Reference

  • src/server.ts:216-288 (registration)
    Registration of the 'submit_workshop' MCP tool, including name, description, and detailed JSON input schema.
    {
      name: "submit_workshop",
      description: "Submit a workshop activity draft",
      inputSchema: {
        type: "object",
        properties: {
          title: {
            type: "string",
            description: "What was the name of your workshop session?",
            minLength: 3,
            maxLength: 200,
          },
          description: {
            type: "string",
            description: "What was it about?",
            maxLength: 2000,
          },
          activityDate: {
            type: "string",
            pattern: "^\\d{4}-\\d{2}-\\d{2}$",
            description: "Date of your workshop (YYYY-MM-DD format)",
          },
          tags: {
            type: "array",
            items: { type: "string" },
            description: "Tags (optional)",
            minItems: 0,
          },
          metrics: {
            type: "object",
            properties: {
              attendees: {
                type: "integer",
                minimum: 1,
                description: "How many people have been trained?",
              },
            },
            required: ["attendees"],
          },
          eventFormat: {
            type: "string",
            enum: Object.values(EventFormat),
            description: "Select event format",
          },
          country: {
            type: "string",
            enum: Object.values(Country),
            description: "Country (required if eventFormat is In-Person or Hybrid)",
          },
          inPersonAttendees: {
            type: "integer",
            minimum: 0,
            description: "In-person attendees (required if eventFormat is Hybrid or In-Person)",
          },
          activityUrl: {
            type: "string",
            maxLength: 500,
            pattern: "^https?://.*",
            description: "Workshop/event link",
          },
          additionalInfo: {
            type: "string",
            maxLength: 2000,
            description: "Additional information (optional)",
          },
          private: {
            type: "boolean",
            description: "Do you want to make this activity private? (optional)",
          },
        },
        required: ["title", "description", "activityDate", "metrics", "eventFormat", "activityUrl"],
      },
    },
  • Core handler implementation: submits workshop activity draft via POST to /activity-drafts/workshop endpoint, handles errors and success responses.
    private async submitActivityDraft(
      endpoint: string,
      data:
        | ContentCreationDraft
        | PublicSpeakingDraft
        | WorkshopDraft
        | MentoringDraft
        | ProductFeedbackDraft
        | GooglerInteractionDraft
        | StoryDraft,
    ): Promise<{
      content: Array<{
        type: string;
        text: string;
      }>;
    }> {
      const url = `${this.baseUrl}/activity-drafts/${endpoint}`;
    
      try {
        const response = await fetch(url, {
          method: "POST",
          headers: {
            "Content-Type": "application/json",
            Authorization: `Bearer ${this.accessToken}`,
          },
          body: JSON.stringify(data),
        });
    
        if (!response.ok) {
          const errorText = await response.text();
          let errorMessage = `GDE API error (${response.status})`;
    
          if (response.status === 401) {
            errorMessage = "❌ GDE authentication failed. Your ADVOCU_ACCESS_TOKEN may be expired or invalid.\n\nPlease check your Advocu access token configuration.";
          } else if (response.status === 400) {
            errorMessage = `❌ GDE API rejected the request:\n\n${errorText}\n\nPlease check:\n- All required fields are present\n- Field values match expected formats\n- Tags are valid\n- Date format is correct (YYYY-MM-DD)`;
          } else if (response.status === 429) {
            errorMessage = "⏱️ GDE API rate limit exceeded (30 requests/minute). Please wait and try again.";
          } else {
            errorMessage = `❌ GDE API error (${response.status}):\n\n${errorText}`;
          }
    
          // Return error as content instead of throwing
          return {
            content: [
              {
                type: "text",
                text: errorMessage,
              },
            ],
          };
        }
    
        const result = (await response.json()) as Record<string, unknown>;
    
        return {
          content: [
            {
              type: "text",
              text: `✅ GDE Activity draft submitted successfully!\n\nEndpoint: ${endpoint}\nStatus: ${response.status}\nResponse: ${JSON.stringify(result, null, 2)}`,
            },
          ],
        };
      } catch (error) {
        if (error instanceof McpError) {
          throw error;
        }
        const errorMsg = this.getErrorMessage(error);
        throw new McpError(
          ErrorCode.InternalError,
          `❌ Failed to submit GDE activity:\n\n${errorMsg}\n\nEndpoint: ${endpoint}`
        );
      }
    }
  • Dispatch case in tool request handler that routes 'submit_workshop' calls to the shared submitActivityDraft function with workshop-specific endpoint and type.
    case "submit_workshop":
      return await this.submitActivityDraft("workshop", args as unknown as WorkshopDraft);
  • TypeScript interface defining the structure of WorkshopDraft input, used for type safety in the handler.
    export interface WorkshopDraft extends ActivityDraftBase {
      /** Metrics related to training reach */
      metrics: {
        /** Number of people who have been trained */
        attendees: number;
      };
      /** Format of the event (In-Person, Virtual, or Hybrid) */
      eventFormat: EventFormat;
      /** Country where the event took place (required if eventFormat is In-Person or Hybrid) */
      country?: Country;
      /** Number of in-person attendees (required if eventFormat is Hybrid or In-Person) */
      inPersonAttendees?: number;
      /** URL link to the workshop or event */
      activityUrl: string;
    }
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 but provides minimal information. 'Submit a workshop activity draft' implies a write/mutation operation but doesn't clarify permissions needed, whether this creates a new record or updates existing ones, what happens on success/failure, or any rate limits. For a mutation tool with 11 parameters and no annotation coverage, this is inadequate behavioral context.

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 a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized and front-loaded with the essential information. There's zero waste or redundancy in the phrasing.

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?

For a mutation tool with 11 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what 'submit' means operationally, what happens after submission, whether there's a review process, or what the expected response format might be. The high parameter count and mutation nature demand more contextual information than provided.

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 91% (high), so the schema already documents most parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema. The baseline score of 3 is appropriate when the schema does the heavy lifting, though the description doesn't compensate for the remaining 9% coverage gap or provide any high-level parameter 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 'Submit a workshop activity draft' clearly states the verb ('submit') and resource ('workshop activity draft'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling tools like 'submit_content_creation' or 'submit_public_speaking' - all appear to be submission tools for different activity types without clear distinction in the description alone.

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 siblings. While the name suggests it's for workshop activities, there's no explicit comparison to 'submit_content_creation' or 'submit_public_speaking' that might also involve workshops. The description lacks any 'when to use' or 'when not to use' context, nor does it mention prerequisites or alternative tools.

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

Related 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/carlosazaustre/advocu-mcp-server'

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