Brawler MCP Server (Python)

Unknown Task

unknown_task

Resolve an unrecognized task query by defaulting it to completion, helping MCP clients handle unknown task values predictably.

Instructions

mcp_server.task that is not a Task value defaults to completion.

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": {
      "q": "<q>"
    },
    "name": "unknown_task"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 26, 2026

TDQS

D1.1/5.0

Behavior1/5

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

No annotations are provided, so the description carries the full disclosure burden, and it discloses nothing actionable — no mutation/read semantics, side effects, permissions, or failure behavior. The 'defaults to completion' phrase is too cryptic to inform an agent about behavior.

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?

It is short, but the brevity comes from under-specification rather than economy. The one sentence is front-loaded with an unparseable internal reference and conveys no usable lead information.

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?

Although an output schema exists (so return values needn't be described), the definition leaves the tool's basic purpose, its sole parameter, and all behavioral traits unexplained. For a tool with one undocumented required parameter, this is wholly inadequate.

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 single required parameter 'q' has 0% schema description coverage and is never mentioned in the description. The agent has no idea what 'q' should contain (a query? a task id? free text?).

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

Purpose1/5

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

The description is a sentence fragment referencing an internal symbol (``mcp_server.task``) and a 'defaults to completion' rule. It never states what the tool does, what resource it operates on, or how it differs from siblings like 'policies', 'echo', or 'route'.

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?

There is no indication of when to call this tool, when to prefer an alternative sibling, or what preconditions exist. The single sentence describes a fallback rule, not a usage policy.

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

Deploy Server