Skip to main content
Glama
Sign In
Agentic Control Framework (ACF)

Agentic Control Framework (ACF)

by FutureAtoms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

defer_task_priority

Defer a task's execution by adjusting its priority by a specified amount. Manage task scheduling order.

Instructions

Defer task priority

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": {
      "id": "<id>"
    },
    "name": "defer_task_priority"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
amountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

D1.3/5.0
Behavior1/5

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

With no annotations, the description must carry the full burden of behavioral disclosure, but it provides none. It does not state whether the action is destructive, reversible, or requires permissions.

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?

While extremely concise (one phrase), it sacrifices necessary specification. It is under-informative rather than efficiently clear.

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

Completeness1/5

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

Given the presence of similar sibling tools and no output schema, the description is woefully incomplete. It fails to explain return values, side effects, or how it differs from related tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has two parameters (id, amount) with no descriptions. The description adds no meaning to these parameters, leaving their purpose and relationship unclear.

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 'Defer task priority' is essentially a tautology of the tool name. It does not clarify what 'defer' means in this context (e.g., postpone, lower priority) or distinguish it from siblings like deprioritize_task or bump_task_priority.

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

Usage Guidelines1/5

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

No usage guidance is provided. The description fails to indicate when to use this tool versus alternatives, nor does it mention any prerequisites or consequences.

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