Skip to main content
Glama

AroFlo: Get LastUpdate

aroflo_get_lastupdate
Read-onlyIdempotent

Query the AroFlo lastupdate zone to retrieve incremental data for synchronization workflows, enabling efficient data updates.

Instructions

Query the AroFlo lastupdate zone for incremental sync workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneNameNo
sinceUtcNo
orderDirectionNoasc
pageNo
pageSizeNo
modeNo
verboseNo
debugNo
rawNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'aroflo_get_lastupdate' tool, which constructs the query parameters and calls the AroFlo client.
    async (args) => {
      const mode = resolveOutputMode(args);
      const envelopeRequested =
        typeof args.mode === 'string' || Boolean(args.raw) || Boolean(args.verbose);
      try {
        const where: string[] = [];
        if (args.zoneName) {
          where.push(`and|zonename|=|${args.zoneName}`);
        }
        if (args.sinceUtc) {
          where.push(`and|lastupdateutc|>|${args.sinceUtc}`);
        }
    
        const response = await client.get('lastupdate', {
          where,
          order: [`lastupdateutc|${args.orderDirection}`],
          page: args.page,
          pageSize: args.pageSize
        });
    
        if (!envelopeRequested) {
          return successToolResult(response);
        }
    
        const out = buildZoneDataEnvelope({
          zone: 'LastUpdate',
          response,
          page: args.page,
          pageSize: args.pageSize,
          mode,
          debug:
            mode === 'debug' || mode === 'raw'
              ? {
                  zone: 'LastUpdate',
                  normalized: {
                    where,
                    order: [`lastupdateutc|${args.orderDirection}`],
                    page: args.page,
                    pageSize: args.pageSize
                  }
                }
              : undefined
        });
    
        return successToolResult(out);
      } catch (error) {
        return errorToolResult(error, { mode, debug: { zone: 'LastUpdate' } });
      }
    }
  • The registration of the 'aroflo_get_lastupdate' tool within the MCP server using registerTool.
    server.registerTool(
      'aroflo_get_lastupdate',
      {
        title: 'AroFlo: Get LastUpdate',
        description: 'Query the AroFlo lastupdate zone for incremental sync workflows.',
        inputSchema,
        // MCP SDK expects output schemas to be object schemas (or raw object shapes).
        // `z.any()` causes output validation to crash under the current SDK.
        outputSchema: z.object({}).passthrough(),
        annotations: {
          readOnlyHint: true,
          idempotentHint: true,
          openWorldHint: true
        }
      },
  • The input schema definition for the 'aroflo_get_lastupdate' tool.
    const inputSchema = {
      zoneName: z.string().min(1).optional(),
      sinceUtc: z.string().min(1).optional(),
      orderDirection: z.enum(['asc', 'desc']).default('asc'),
      page: z.number().int().positive().default(1),
      pageSize: z.number().int().positive().max(500).optional(),
      mode: z.enum(['data', 'verbose', 'debug', 'raw']).optional(),
      verbose: z.boolean().optional(),
      debug: z.boolean().optional(),
      raw: z.boolean().optional()
    };
Behavior3/5

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

Annotations declare readOnly/idempotent safety; description adds 'incremental sync' context implying time-based filtering. However, it omits behavioral details like valid 'zoneName' values, pagination limits (max 500), or how 'mode'/'verbose' flags alter output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single 9-word sentence with no redundancy. However, extreme brevity is inappropriate for a 9-parameter tool with zero schema documentation; it under-delivers rather than being optimally concise.

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?

Inadequate for complexity: 9 undocumented parameters require examples (valid zones), format guidance (UTC timestamps), and pagination logic. Output schema exists but description doesn't reference return structure or how incremental cursors work.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (critical failure). Description fails to compensate: 'zoneName' valid values are unspecified, 'sinceUtc' format is undocumented, and boolean flags (verbose/debug/raw) lack behavioral explanation despite being central to the tool's operation.

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?

Uses specific verb 'Query' and identifies the resource 'lastupdate zone' and use case 'incremental sync workflows,' distinguishing it from sibling full-fetch tools like 'aroflo_get_tasks'. Minor opacity around 'zone' jargon prevents a 5.

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

Usage Guidelines3/5

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

Implies usage context ('incremental sync workflows') but provides no explicit guidance on when to use this versus 'aroflo_query_zone' or specific entity getters, and fails to note that all 9 parameters are optional (0 required).

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/0x1NotMe/aroflo-mcp'

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