Skip to main content
Glama
Sign In
crewchat

crewchat

by deepankar17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

hub_answer

Submit advice for a hub_ask question and record an approve or changes verdict for a task.

Instructions

Answer a hub_ask question (advisors). For a task: approve or changes.

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": {
      "id": "<id>",
      "text": "<text>"
    },
    "name": "hub_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe question.
textYesYour advice.
verdictNoFor a task.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.2
    • changedInput schema / properties / id / description
      Previous value: -"The question's number."New value: +"The question."
    • changedInput schema / properties / verdict / description
      Previous value: -"For a question about a task: approve, or changes (say what is missing)."New value: +"For a task."
  2. Addedv0.14.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is partly given. The description adds advisor context and the verdict behavior for tasks, but it does not explain side effects, whether answers are visible or editable, or any permission/auth requirements.

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?

Two short sentences are front-loaded with the action and a key task-specific rule, with no filler. The fragment 'For a task: approve or changes.' is slightly cryptic but still economical.

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 three-parameter tool with full schema coverage and annotations covering side effects, the description supplies the essential trigger and verdict guidance. It leaves some ambiguity about whether verdict is required for task questions, but the schema marks it optional.

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 coverage is 100%, so the schema documents id='The question', text='Your advice', and the verdict enum. The description adds only a brief cue that verdict is 'For a task: approve or changes,' which largely restates the verdict schema; baseline 3 applies.

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 gives a specific verb ('Answer') and resource ('hub_ask question'), so the core action is clear. It does not explicitly distinguish this from other hub_* siblings such as hub_send or hub_task, but naming hub_ask anchors its role.

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

Usage Guidelines4/5

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

It states the trigger—answer a hub_ask question—and adds that a task question uses approve/changes. It does not name when not to use it or point to an alternative sibling.

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