Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_sidequests_comprehensive

Read-onlyIdempotent

Retrieve sidequests with comprehensive filters including status, priority, creation or update dates, and links to tasks or subtasks for precise retrieval.

Instructions

Advanced sidequest 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_sidequests_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 paused task
subtask_idNoFilter by paused subtask
priorityNo'low', 'medium', 'high', 'critical'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds no additional behavioral context. It does not describe what happens with missing filters, pagination, or performance implications, leaving the agent without useful operational details.

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 extremely concise (two words) but lacks substantive content. It is not front-loaded with key information; a minimal viable description would at least state the purpose clearly.

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 tool has 7 parameters and no output schema, the description is too brief to fully inform an agent. It does not explain the scope of search, relationship to sibling tools, or behavior when parameters are omitted.

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 description coverage is 100%, so the schema already documents all parameters with descriptions. The description adds no extra meaning beyond 'Advanced sidequest search'. Baseline of 3 is appropriate.

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 'Advanced sidequest search' clearly indicates this tool retrieves sidequests with advanced filtering. The name 'get_sidequests_comprehensive' reinforces that it fetches sidequests comprehensively, distinguishing it from siblings like 'get_sidequest_files' or 'get_incomplete_sidequests'.

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 explicit guidance on when to use this tool versus alternatives such as 'get_incomplete_sidequests' or 'get_sidequest_files'. The description does not mention prerequisites, exclusions, or scenarios where other tools would be more appropriate.

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