Skip to main content
Glama
Sign In
Python MCP Toolkit Server

Python MCP Toolkit Server

by linhanhan227
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

agent

Manage lightweight task status: record goals, steps, progress, and results. Supports start, status, update, finish, and reset actions.

Instructions

管理一个轻量 agent 任务状态，用于记录目标、步骤、进展和完成结果。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoagent 动作：start/status/update/finish/reset。status
taskNostart 时设置的任务目标。
stepsNostart 时设置的执行步骤；为空时使用默认执行步骤。
noteNoupdate/finish 时追加的进展、观察或结论。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention side effects (e.g., state mutation), authentication requirements, rate limits, or lifecycle behavior of actions (start, update, finish, reset). This is insufficient for a tool managing task state.

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?

The description is a single sentence, making it concise. It is front-loaded with the core purpose. However, it could be slightly more detailed without losing conciseness. Overall, it earns its place.

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?

Given the moderate complexity (4 parameters, actions enum) and the presence of an output schema, the description is minimally adequate. It explains the high-level purpose but lacks details on action semantics, required states, and usage flow, making it incomplete for full guidance.

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 description coverage is 100%, so each parameter already has a description. The tool description adds no additional meaning beyond the schema. Baseline is 3, and the description does not compensate with extra context.

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 the tool manages agent task status and records goals, steps, progress, and results. This is clear and distinguishes it from sibling tools (file_operation, web_search) which have different domains. However, the verb 'manage' is somewhat broad; a more specific verb like 'track' would improve clarity.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention context, prerequisites, or exclusions. Sibling tools are quite different, but explicit when-to-use instructions are absent.

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