Skip to main content
Glama

AroFlo: Get Record

aroflo_get_record
Read-onlyIdempotent

Fetch a specific AroFlo record by specifying zone, ID field, and value. Add extraWhere clauses for filtering and choose output modes like data or verbose.

Instructions

Fetch one specific AroFlo record by zone and ID field/value. Use extraWhere for additional pipe-delimited clauses like "and|archived|=|false".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneYes
idFieldYes
idValueYes
extraWhereNo
modeNo
verboseNo
debugNo
rawNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler function for 'aroflo_get_record' which calls the AroFlo client to fetch records.
    async (args) => {
      const mode = resolveOutputMode(args);
      const envelopeRequested =
        typeof args.mode === 'string' || Boolean(args.raw) || Boolean(args.verbose);
      try {
        const extraWhere =
          typeof args.extraWhere === 'string' ? [args.extraWhere] : args.extraWhere;
        const where = [`and|${args.idField}|=|${String(args.idValue)}`, ...(extraWhere ?? [])];
    
        const response = await client.get(args.zone, {
          where,
          page: 1,
          pageSize: 1
        });
    
        if (!envelopeRequested) {
          return successToolResult(response);
        }
    
        const out = buildZoneDataEnvelope({
          zone: args.zone,
          response,
          page: 1,
          pageSize: 1,
          mode,
          debug:
            mode === 'debug' || mode === 'raw'
              ? {
                  zone: args.zone,
                  normalizedParams: { where, page: 1, pageSize: 1 }
                }
              : undefined
        });
    
        return successToolResult(out);
      } catch (error) {
        return errorToolResult(error, { mode, debug: { zone: args.zone, idField: args.idField } });
      }
    }
  • Zod schema definition for the input arguments of the tool.
    const inputSchema = {
      zone: z.string().min(1),
      idField: z.string().min(1),
      // JSON Schema cannot represent BigInt, so accept string/number only.
      // For large numeric IDs, pass them as strings.
      idValue: z.union([z.string().min(1), z.number()]),
      extraWhere: stringOrStringArraySchema.optional(),
      mode: z.enum(['data', 'verbose', 'debug', 'raw']).optional(),
      verbose: z.boolean().optional(),
      debug: z.boolean().optional(),
      raw: z.boolean().optional()
    };
  • Registration of the 'aroflo_get_record' tool with the MCP server.
    export function registerGetRecordTool(server: McpServer, client: AroFloClient): void {
      server.registerTool(
        'aroflo_get_record',
        {
          title: 'AroFlo: Get Record',
          description:
            'Fetch one specific AroFlo record by zone and ID field/value. ' +
            'Use extraWhere for additional pipe-delimited clauses like "and|archived|=|false".',
          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
          }
        },
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, confirming safe read behavior. The description adds value by specifying 'one specific' record (implying singleton return vs. list) and documenting the pipe-delimited clause format for extraWhere. However, it omits behavioral details for the mode enum and boolean flags (verbose/debug/raw), which overlap in naming and need clarification.

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?

The description consists of two efficient sentences with no wasted words. The first establishes purpose and main parameters; the second provides essential syntax guidance for the complex extraWhere parameter. However, given the severe lack of schema documentation, the structure could have been improved by referencing the existence of output formatting options (mode/verbose/debug/raw).

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 8 parameters with 0% schema coverage and no inline documentation, the description is insufficiently complete. While it covers the primary retrieval path, it leaves half the parameters (mode, verbose, debug, raw) completely undocumented, leaving users to guess their purpose and interaction with the output schema.

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?

With 0% schema description coverage, the description carries the full burden of parameter documentation. While it explains zone, idField/idValue, and extraWhere (with syntax), it completely omits the mode enum (data/verbose/debug/raw) and the boolean flags (verbose, debug, raw), leaving 4 of 8 parameters undocumented and unexplained.

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 core action ('Fetch one specific AroFlo record') and identifies the required identifying parameters ('zone and ID field/value'). However, it fails to differentiate this generic record getter from the numerous specific entity getters (e.g., aroflo_get_tasks, aroflo_get_projects) available as siblings, leaving ambiguity about which to use.

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?

The description provides valuable syntax guidance for the extraWhere parameter with a concrete example ('and|archived|=|false'), helping users construct valid queries. However, it lacks explicit guidance on when to use this generic tool versus the many specific entity getters (aroflo_get_tasks, etc.) or the aroflo_create_or_update_record sibling.

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