Skip to main content
Glama

get_tasks

Read-onlyIdempotent

Retrieve farm management tasks, newest due date first by default (tasks without a due date last). Filters: status (Pending | In Progress | Completed, case-insensitive, string or array; omit for all), excludeCompleted, dueFrom/dueTo (inclusive YYYY-MM-DD in the farm timezone, default America/New_York), assignedTo, titleContains. Paginate by passing the returned nextCursor as cursor with the same filters. Requires farmId and apiKey authorization.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "farmId": "<farmId>"
    },
    "name": "get_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort order by due date (default: dueDate_desc)
dueToNoFilter tasks due on or before YYYY-MM-DD (farm timezone, default America/New_York)
limitNoMaximum tasks to return (1-100, default 25)
cursorNoPagination cursor for next page (pass nextCursor)
farmIdYesThe unique farm ID
statusNoTask status filter: Pending, In Progress, Completed (string or array). Case-insensitive. Omit for all statuses.
dueFromNoFilter tasks due on or after YYYY-MM-DD (farm timezone, default America/New_York)
assignedToNoFilter by assigned user ID, name, or email (case-insensitive exact match)
titleContainsNoFilter tasks by title substring (case-insensitive)
excludeCompletedNoExclude completed tasks

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / properties / assignedTo
      Added value: +{
      +  "description": "Filter by assigned user ID, name, or email (case-insensitive exact match)",
      +  "type": "string"
      +}
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "Pagination cursor for next page (pass nextCursor)",
      +  "type": "string"
      +}
    • addedInput schema / properties / dueFrom
      Added value: +{
      +  "description": "Filter tasks due on or after YYYY-MM-DD (farm timezone, default America/New_York)",
      +  "type": "string"
      +}
    • addedInput schema / properties / dueTo
      Added value: +{
      +  "description": "Filter tasks due on or before YYYY-MM-DD (farm timezone, default America/New_York)",
      +  "type": "string"
      +}
    • addedInput schema / properties / excludeCompleted
      Added value: +{
      +  "description": "Exclude completed tasks",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Maximum tasks to return (1-100, default 25)",
      +  "type": "integer"
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "Sort order by due date (default: dueDate_desc)",
      +  "enum": [
      +    "dueDate_desc",
      +    "dueDate_asc"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / status / description
      Previous value: -"Optional task status filter: Pending, In Progress"New value: +"Task status filter: Pending, In Progress, Completed (string or array). Case-insensitive. Omit for all statuses."
    • addedInput schema / properties / status / oneOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  }
      +]
    • removedInput schema / properties / status / type
      Removed value: -"string"
    • addedInput schema / properties / titleContains
      Added value: +{
      +  "description": "Filter tasks by title substring (case-insensitive)",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value: default sort direction, where undated tasks land, the farm-timezone default, the auth requirement (farmId + apiKey), and the rule that pagination requires repeating the same filters with nextCursor.

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?

A single front-loaded paragraph that leads with verb, resource, and ordering, then filters, then pagination, then auth. Efficient, though the filter list partially duplicates schema text that the agent will see anyway.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 10 parameters and no output schema, the description covers ordering, filtering, pagination, and auth, and even hints at the nextCursor return value. The only gap is that it never sketches what a returned task record contains, which the missing output schema would otherwise have to supply.

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 coverage is 100%, so every parameter is already documented with the same details (enums, defaults, formats). The description largely restates those filters in prose rather than adding syntax or edge-case meaning, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (retrieve) and resource (farm management tasks) plus the default ordering behavior. It is unmistakably the read/list tool versus siblings like create_task, update_task, complete_task, and delete_task, so an agent can select it without opening the schema.

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

Usage Guidelines4/5

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

Gives concrete filter usage rules (status values, case-insensitivity, string or array, 'omit for all'), date-range semantics, and how to paginate. It does not explicitly name alternatives or when NOT to use it, but the context for calling it is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources