Skip to main content
Glama
Sign In
Agent-Comm-Hub

Agent-Comm-Hub

by liuboacean
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

propose_strategy

Propose a strategy for agent collaboration. Admin approval is required before other agents can adopt it; the hub auto-classifies sensitivity.

Instructions

提议一个策略。策略需 admin 审批后才能被其他 Agent 搜索和采纳。Hub 会自动判定敏感级别。

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>",
      "content": "<content>",
      "category": "<category>"
    },
    "name": "propose_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes策略标题
contentYes策略内容（Markdown，最多 5000 字符）
task_idNo关联任务 ID
categoryYes策略分类

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.6

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided. Description discloses that admin approval is required before the strategy is searchable/adoptable and that Hub auto-determines sensitivity, but lacks details on side effects, mutability, or error handling.

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?

Description is short (two sentences in Chinese), front-loaded with the action, and every sentence provides necessary context. Slightly more structured detail could improve it.

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?

Adequate for a 4-param tool with no output schema, but missing return value info and does not mention error states. Description covers primary purpose and approval flow insufficiently.

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 baseline is 3. Description adds no additional meaning beyond what is already in the schema for parameters title, content, category, and task_id.

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

Purpose5/5

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

Description clearly states the verb '提议' (propose) and resource '策略' (strategy), and distinguishes from siblings by adding context about admin approval and automatic sensitivity detection.

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

Usage Guidelines3/5

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

Description implies usage for proposing new strategies with approval needed, but does not explicitly state when to use this tool versus alternatives like propose_strategy_tiered or other strategy-related tools.

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