Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_subtasks_comprehensive

Read-onlyIdempotent

Search subtasks using filters for status, priority, date ranges, and task ID. Configure result limits for tailored output.

Instructions

Advanced subtask search

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_subtasks_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]
task_idNoFilter by task
priorityNo'low', 'medium', 'high', 'critical'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description's burden is lower. However, the description adds no behavioral traits like return format or filtering behavior, leaving gaps in transparency.

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

Conciseness2/5

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

At three words, it is concise but insufficiently informative. The description is under-specified and does not earn its place by providing necessary detail.

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 complexity (6 parameters, no output schema) and many sibling tools, the description is too sparse. It lacks completeness for an AI agent to use effectively.

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% with descriptions for all 6 parameters. The description does not add new meaning beyond the schema, so baseline score of 3 is appropriate.

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

Purpose2/5

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

The description 'Advanced subtask search' is vague and does not specify what the tool returns or its scope. It fails to distinguish from siblings like 'get_subtasks_by_task' which are more specific.

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 on when to use this tool versus alternatives such as 'get_subtasks_by_task' or 'get_incomplete_subtasks'. The description does not mention context or exclusions.

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