Skip to main content
Glama
Sign In
wise-council-mcp

wise-council-mcp

by Dream22180971
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

consult

Select an expert advisor and submit your question to receive specialized guidance from their unique perspective.

Instructions

向智囊团中的单个专家咨询问题。选择一位专家，获取其专业视角的建议。

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": {
      "advisor": "<advisor>",
      "question": "<question>"
    },
    "name": "consult"
  }
}

Input Schema

NameRequiredDescriptionDefault
advisorYes专家ID，可选值：zhangxiaolong, yujun, mikecohn, martinfowler, unclebob, donnorman, stevekrug, evanyou, linus, guido, jamesbach, kelseyhightower, michaelstonebraker, wernervogels, wangjian, bruceschneier, wuhuanqing, djpatil, zhoujingren, brendangregg, yangtao, ruanyifeng, laozi, sunzi, wangyangming, zhuangzi, guiguzi, hanfeizi, viktorfrankl, camus, adler, jung, yangjiang, shitieteng, epictetus, kahneman, munger, future-self
contextNo项目上下文（可选）：项目类型、技术栈、团队规模等
questionYes要咨询的问题或需要分析的方案

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns advice from an expert, but it gives no detail on response format, limitations, side effects, or any behavioral nuance beyond that basic promise.

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 extremely concise: two short sentences with no filler. The core action is front-loaded, and every phrase serves a purpose.

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

Completeness4/5

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

For a simple 3-parameter advice tool with no output schema, the description conveys the essential call pattern: select a single expert and ask a question. Optional context is documented in the schema. It omits guidance on which expert to choose or what the response will look like, but these are minor gaps for a tool of this simplicity.

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 the baseline is 3. The description only loosely maps to parameters ('choose an expert' to advisor, 'ask a question' to question) and does not add extra meaning or usage detail for the parameters beyond what the schema already provides.

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?

The description states a specific action and resource: '向智囊团中的单个专家咨询问题' (consult a single expert in the think tank). It also distinguishes itself from group-oriented siblings by emphasizing '单个专家' (single expert), making its scope clear.

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?

The description implies usage when a single expert perspective is needed, but it does not explicitly name alternatives or state when not to use this tool. Guidance is left to inference rather than being stated directly.

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