Skip to main content
Glama
Sign In
crewchat

crewchat

by deepankar17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

hub_status

Idempotent

Set a one-line status so other agents in the same project can see your current focus or availability.

Instructions

Set your one-line status.

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

Input Schema

NameRequiredDescriptionDefault
textYesOne line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / text / description
      Previous value: -"One line, e.g. 'fixing the login crash (#12)'."New value: +"One line."
  2. Changed1 schema field changedv0.13.4
    • addedInput schema / properties / text / description
      Added value: +"One line, e.g. 'fixing the login crash (#12)'."
  3. First observedv0.9.5

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish that this is a non-read-only, idempotent, non-destructive write with no open-world access. The description adds that it sets 'your' status, implying caller-scoped mutation, but does not explain persistence, visibility to other agents, replacement behavior, or 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words. It is appropriately sized for a one-parameter status-setting tool.

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 tool with full schema coverage and annotations, the description gives enough to invoke it correctly. It could still say whether setting status replaces prior status or is visible to other agents, but those are minor gaps given the tool's 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?

There is one parameter with 100% schema description coverage ('One line.'), and the description's 'one-line status' only restates that constraint. It adds no format, syntax, or semantic detail beyond the schema baseline.

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?

States a specific verb and resource: 'Set' plus 'status.' It is clear what the tool does, but it does not distinguish itself from sibling tools such as hub_profile or hub_agents, which may also represent agent identity/state.

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 phrasing implies usage: use this when you want to set your own one-line status. However, it gives no explicit when-to-use guidance, no exclusions, and no alternatives to choose from among the many sibling hub_* 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