Skip to main content
Glama
janetsep

TreePod Financial MCP Agent

by janetsep

Verificar ocupación

check_occupancy

Check current and future occupancy status of domes using real-time data to support financial planning and business reporting.

Instructions

Verifica estado de ocupación actual y futura de los domos basado en datos reales

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_rangeNotoday

Implementation Reference

  • The handler function for the 'check_occupancy' tool. It processes the date_range parameter (default 'today'), retrieves corresponding occupancy data from treepodData, constructs a formatted text response with occupied/available/total pods, rate, and status message, and sets it as toolResult content.
    case 'check_occupancy':
      const dateRange = args?.date_range || 'today';
      const occupancyData = treepodData.occupancy[dateRange];
    
      let occupancyText = `🏕️ ESTADO DE OCUPACIÓN TREEPOD (${dateRange.toUpperCase()})\n\n`;
      occupancyText += `✅ Ocupados: ${occupancyData.occupied} pods\n`;
      occupancyText += `🟢 Disponibles: ${occupancyData.available} pods\n`;
      occupancyText += `📊 Total: ${occupancyData.total} pods\n`;
      occupancyText += `📈 Tasa ocupación: ${occupancyData.rate}%\n\n`;
      occupancyText += occupancyData.rate >= 80 ? '🔥 ¡Excelente ocupación!' : 
                      occupancyData.rate >= 60 ? '👍 Buena ocupación' : 
                      '⚠️ Ocupación baja - considerar promociones';
    
      toolResult = {
        content: [{ type: "text", text: occupancyText }]
      };
      break;
  • Registration of the 'check_occupancy' tool in the tools/list MCP method response, including name, description, and inputSchema defining the date_range parameter.
    {
      name: "check_occupancy",
      description: "Verifica el estado actual de ocupación de los TreePods",
      inputSchema: {
        type: "object",
        properties: {
          date_range: {
            type: "string",
            enum: ["today", "week", "month"],
            description: "Rango de fechas para consultar",
            default: "today"
          }
        }
      }
    }
  • Input schema for the check_occupancy tool, specifying date_range as a string enum with values 'today', 'week', 'month' and default 'today'.
    inputSchema: {
      type: "object",
      properties: {
        date_range: {
          type: "string",
          enum: ["today", "week", "month"],
          description: "Rango de fechas para consultar",
          default: "today"
        }
      }
    }
  • Static data structure providing occupancy information for different date ranges (today, week, month), used directly by the check_occupancy handler.
    occupancy: {
      today: { occupied: 12, available: 3, total: 15, rate: 80 },
      week: { occupied: 78, available: 27, total: 105, rate: 74 },
      month: { occupied: 310, available: 155, total: 465, rate: 67 }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool checks occupancy status based on real data, but doesn't describe what 'real data' entails, whether it's read-only or has side effects, response format, error conditions, or rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 in Spanish that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with every part contributing to understanding what the tool does.

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 tool's complexity (checking current and future occupancy), lack of annotations, no output schema, and incomplete parameter documentation (0% schema coverage), the description is insufficient. It doesn't explain what 'occupancy status' includes, how 'future' is defined, what 'real data' means, or what the return values look like. For a forecasting/status tool with no structured support, more detail is 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 description doesn't mention any parameters, while the input schema has one parameter ('date_range') with 0% schema description coverage. Since there's only one parameter and the description doesn't add any semantic information about it, the baseline score is 3. The description doesn't compensate for the lack of schema documentation, but the low parameter count keeps it from being lower.

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 tool's purpose: 'Verifica estado de ocupación actual y futura de los domos basado en datos reales' (Checks current and future occupancy status of domes based on real data). It specifies the verb ('verifica'), resource ('domos'), and scope ('actual y futura'), but doesn't explicitly differentiate from sibling tools like 'get_business_status' or 'predict_revenue' which might overlap in domain.

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, exclusions, or compare it to sibling tools like 'get_business_status' (which might include occupancy) or 'predict_revenue' (which could involve occupancy forecasting). Usage context is implied but not explicit.

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/janetsep/treepod-financial-mcp'

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