Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_tasks_comprehensive

Read-onlyIdempotent

Search tasks using multiple filters like status, date range, milestone, and priority to find specific project tasks efficiently.

Instructions

Advanced task search with multiple filters

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_tasks_comprehensive"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo'pending', 'in_progress', 'completed', 'blocked' (NULL = all)
limitNoMaximum results
date_range_createdNo[start_date, end_date]
date_range_updatedNo[start_date, end_date]
milestone_idNoFilter by milestone
priorityNo'low', 'medium', 'high', 'critical'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

C2.5/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and idempotentHint=true, indicating a safe, non-destructive read operation. The description adds no behavioral details beyond the annotations, such as pagination behavior, result set characteristics, or performance implications. Therefore, it provides minimal additional transparency.

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

Conciseness3/5

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

The description is a single sentence, making it concise, but it is too vague to be informative. It lacks structure and does not front-load critical details. Every word should earn its place, but here the sentence is generic.

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 presence of multiple sibling tools, 6 parameters, and no output schema, the description is insufficient. It does not explain the return format, filtering behavior, or how this tool fits among alternatives. It leaves significant gaps for effective agent use.

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 input schema covers all 6 parameters with descriptions (100% coverage), so the baseline is 3. The description ('multiple filters') does not add new meaning beyond what the schema already provides. No parameters are elaborated further.

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

Purpose3/5

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

The description 'Advanced task search with multiple filters' indicates the tool searches tasks with filters, but it lacks specificity about the resource (tasks) and does not distinguish it from sibling tools like get_tasks_by_milestone or get_incomplete_tasks. The verb 'search' is present, but the purpose is not sharply defined.

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?

No guidance is provided on when to use this tool versus alternative task retrieval tools such as get_tasks_by_milestone or get_incomplete_tasks. There is no mention of prerequisites, context, or exclusions, leaving the agent to infer usage.

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

Deploy Server

Other Tools