Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_sidequest

Pause a current task to handle urgent interruptions like bug fixes, blockers, or unexpected work. Create a sidequest with priority and status to track the interruption.

Instructions

Create an urgent interruption that pauses the current task. Use for bug fixes, blockers, or unexpected work discovered mid-task.

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": {
      "paused_task_id": "<paused_task_id>",
      "name": "<name>"
    },
    "name": "add_sidequest"
  }
}

Input Schema

NameRequiredDescriptionDefault
paused_task_idYesID of the task being paused for this sidequest
nameYesSidequest name
statusNoSidequest status (default: pending)pending
priorityNoSidequest priority (default: critical)critical
descriptionNoSidequest description
paused_subtask_idNoIf sidequest during subtask
flow_idsNoJSON array of flow IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations are all false, so the description carries the full burden. It adds key behavioral context: 'pauses the current task' and 'urgent interruption,' which discloses side effects beyond what annotations provide.

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

Conciseness5/5

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

The description is extremely concise (two sentences) and front-loaded with the primary action. Every word adds value.

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?

For a tool with 7 parameters and no output schema, the description covers core usage and context. It omits details like default values but those are in the schema. Overall, it sufficiently guides the agent.

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 the schema already documents all parameters. The description adds no additional parameter-level meaning, earning a baseline score of 3.

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?

The description clearly states the tool creates an urgent interruption that pauses the current task, specifying verb (create) and resource (sidequest). It distinguishes from siblings like add_task and add_subtask by emphasizing urgent interruptions.

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?

The description explicitly states use cases: bug fixes, blockers, or unexpected work discovered mid-task. It implies not for planned work, but does not explicitly exclude other scenarios or mention alternatives.

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