Skip to main content
Glama

ADS Beast

task_create

Create a task for the team in ADS Beast.

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": {
      "title": "<title>",
      "priority": "<priority>"
    },
    "name": "task_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesShort title.
categoryNoFree-form category.
due_dateNoDue date, YYYY-MM-DD.
priorityYeslow, medium, high or urgent.
client_idNo
descriptionNoWhat has to be done.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered externally. In return the description adds almost nothing beyond the annotations: it does not say who the task is assigned to, whether 'for the team' means shared visibility, whether creation is idempotent, or what a caller gets back. For a non-destructive write with open-world side effects, that is a real gap.

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

Conciseness4/5

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

One front-loaded sentence with no filler, which is structurally sound. It is arguably too terse for a six-parameter create tool, but no sentence wastes space.

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

Completeness3/5

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

With no output schema, the description could reasonably have explained what is returned on success (task id, status) and how client_id scopes the task. Annotations and a well-covered schema absorb most of the burden, leaving the thin description adequate but not sufficient on its own.

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 high (83%), so the schema already documents title, priority, due_date, category and description; baseline 3 applies. The description contributes no syntax, defaults, or constraints, and the undocumented client_id parameter gets no clarification here.

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 states a specific verb and resource ('Create a task') and adds a scope hint ('for the team in ADS Beast'). It does not distinguish itself from the close sibling task_suggest or explain how team/task creation differs from other create_* tools, so it stays at clear-but-undifferentiated.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. An agent cannot tell from this sentence whether task_suggest is a prerequisite or a substitute, nor what preconditions (client, team, assignment) apply.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.