Skip to main content
Glama
Sign In
mcp-taskflow

mcp-taskflow

by CalebGerman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

reflect_task

Critically review analysis results to identify potential issues, alternative approaches, and improvements, and propose optimizations for your tasks.

Instructions

Critically review analysis results and propose optimizations. Identifies potential issues, alternative approaches, and improvements.

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": {
      "summary": "<summary>",
      "analysis": "<analysis>"
    },
    "name": "reflect_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
summaryYes
analysisYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries full behavioral burden. It says the tool identifies issues and improvements, but does not disclose whether it is read-only, whether proposals are applied, what permissions are needed, or what it returns.

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 two concise sentences, front-loaded with the core action and then the specific outputs. Every sentence earns its place.

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?

For a tool with two required parameters, no annotations, no output schema, and no parameter descriptions, this description is incomplete. It gives a high-level purpose but omits usage context, parameter meaning, and operational behavior.

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?

Schema description coverage is 0%, so the description must explain the two parameters. It only vaguely references 'analysis results' and says nothing about the required 'summary' parameter or expected formats and limits.

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: 'Critically review analysis results and propose optimizations.' It is clear what the tool does, but it does not mention task context or distinguish itself from siblings like analyze_task or verify_task.

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 explicit guidance on when to use this tool versus alternatives. The implied sequence after analysis is weak, and no exclusions or sibling routing are provided.

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