Skip to main content
Glama
adrielisa

MCP Server: Weather & Upnify Integration

by adrielisa

create-upnify-reminder

Schedule reminders in Upnify agenda by providing subject, description, and start date. Supports weather and CRM integration for streamlined task management.

Instructions

Create a new reminder in Upnify agenda

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asuntoYesSubject/title of the reminder
descripcionYesDescription or details of the reminder
fechaInicioYesStart date and time in format YYYY-MM-DD HH:mm (e.g., "2025-07-26 05:00")

Implementation Reference

  • Executes the tool by authenticating with Upnify, constructing the reminder payload, and sending a POST request to the reminders endpoint.
    async createReminder(tkIntegracion: string, reminderData: ReminderData) {
        try {
            const { token, userInfo } = await this.auth.getTokenAndUserInfo(tkIntegracion);
    
            const upnifyPayload = {
                key: "tkCarpeta",
                tipoCarpeta: "1",
                tkOportunidad: "",
                asunto: reminderData.asunto || "",
                gmt: "10",
                tkProspecto: "",
                search_terms: "",
                descripcion: reminderData.descripcion || "",
                idTipoPendiente: "1",
                frecuencia: "",
                recurrencia: "1",
                terminar: "0",
                diasMes: "1",
                diasRecurrencia: "",
                fechaInicio: reminderData.fechaInicio || ""
            };
    
            const response = await fetch(`${API_URLS.UPNIFY_BASE}${ENDPOINTS.REMINDERS}`, {
                method: 'POST',
                headers: {
                    'token': token,
                    'Content-Type': 'application/json',
                },
                body: JSON.stringify(upnifyPayload)
            });
    
            if (!response.ok) {
                const errorText = await response.text();
                console.error('Payload enviado:', JSON.stringify(upnifyPayload, null, 2));
                console.error('Token usado:', token);
                console.error('Respuesta del servidor:', errorText);
                throw new Error(`Error al crear recordatorio: ${response.status} ${response.statusText}. ${errorText}`);
            }
    
            const result = await response.json();
            return {
                success: true,
                message: 'Recordatorio agendado exitosamente',
                data: result,
                tkEmpresa: userInfo.tkEmpresa
            };
        } catch (error) {
            throw new Error(`Error al agendar recordatorio en Upnify: ${error instanceof Error ? error.message : error}`);
        }
    }
  • Input schema for the tool as registered in the list_tools handler.
    {
        name: 'create-upnify-reminder',
        description: 'Create a new reminder in Upnify agenda',
        inputSchema: {
            type: 'object',
            properties: {
                asunto: {
                    type: 'string',
                    description: 'Subject/title of the reminder'
                },
                descripcion: {
                    type: 'string',
                    description: 'Description or details of the reminder'
                },
                fechaInicio: {
                    type: 'string',
                    description: 'Start date and time in format YYYY-MM-DD HH:mm (e.g., "2025-07-26 05:00")'
                }
            },
            required: ['asunto', 'descripcion', 'fechaInicio']
        }
    },
  • main.ts:406-425 (registration)
    Registration in call_tool handler that validates inputs and delegates to the UtilitiesHandler.createReminder method.
    } else if (name === 'create-upnify-reminder') {
        const { asunto, descripcion, fechaInicio } = args as any;
        if (!asunto || !descripcion || !fechaInicio) {
            return createErrorResponse(
                new Error('Se requieren todos los parámetros: asunto, descripcion, fechaInicio'),
                'Validación de parámetros'
            );
        }
    
        try {
            const result = await utilitiesHandler.createReminder(tkIntegracion, { asunto, descripcion, fechaInicio });
            return createSuccessResponse({
                success: true,
                message: 'Recordatorio agendado exitosamente en Upnify',
                reminder: { asunto, descripcion, fechaInicio },
                data: result.data
            });
        } catch (error) {
            return createErrorResponse(error, 'Error al agendar recordatorio en Upnify');
        }
  • TypeScript interface defining the structure of reminder input data, used by the handler.
    export interface ReminderData {
        asunto: string;
        descripcion: string;
        fechaInicio: string;
    }
  • Input schema in the Python MCP server implementation (note: handler is a TODO stub).
    Tool(
        name="create-upnify-reminder",
        description="Create a new reminder in Upnify agenda",
        inputSchema={
            "type": "object",
            "properties": {
                "asunto": {"type": "string", "description": "Subject/title of the reminder"},
                "descripcion": {"type": "string", "description": "Description or details of the reminder"},
                "fechaInicio": {"type": "string", "description": "Start date and time in format YYYY-MM-DD HH:mm (e.g., \"2025-07-26 05:00\")"}
            },
            "required": ["asunto", "descripcion", "fechaInicio"]
        }
    )
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 'Create a new reminder' implies a write operation, it doesn't specify authentication requirements, rate limits, whether the creation is idempotent, what happens on success/failure, or any side effects. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 any wasted words. It's appropriately sized for a simple creation tool and front-loads the essential information ('Create a new reminder in Upnify agenda').

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?

For a creation tool with no annotations and no output schema, the description provides minimal but adequate context about what it does. However, it lacks important details about behavioral aspects (like what gets returned or error conditions) that would be needed for robust agent usage. The 100% schema coverage helps, but the overall context remains incomplete.

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 all three parameters clearly documented in the input schema. The description adds no additional parameter information beyond what's already in the schema (subject, description, start date/time format). This meets the baseline expectation when the schema does the heavy lifting.

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 action ('Create a new reminder') and the resource ('in Upnify agenda'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its siblings (e.g., create-upnify-opportunity, create-upnify-prospect), which all create different types of Upnify entities but share similar naming patterns.

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. It doesn't mention prerequisites, when this tool is appropriate versus other creation tools (like create-upnify-opportunity), or any contextual constraints. The agent must infer usage from the tool name alone.

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/adrielisa/MCP'

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