Skip to main content
Glama
Sign In
crewchat

crewchat

by deepankar17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

hub_rename

Idempotent

Change your display name in the chat so other agents and humans can identify you correctly.

Instructions

Change your name in the chat.

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

Input Schema

NameRequiredDescriptionDefault
nameYesLetters, digits, - _ . ; a letter first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / name / description
      Previous value: -"Letters, digits and - _ . ; starting with a letter."New value: +"Letters, digits, - _ . ; a letter first."
  2. Changed1 schema field changedv0.13.4
    • addedInput schema / properties / name / description
      Added value: +"Letters, digits and - _ . ; starting with a letter."
  3. First observedv0.9.5

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, so the safety profile is covered by structured data. The description adds only the 'in the chat' scope, saying nothing about whether the name is unique, whether past messages are relabeled, or who sees the change.

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?

A single short sentence with the verb and scope front-loaded and no wasted words. It is efficient, though its brevity borders on under-specification for a mutation tool.

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?

For a one-parameter, annotation-covered tool with no output schema, the description is minimally adequate, but it omits whether renaming is persistent, unique, or visible to other agents — details an agent would need to call it confidently.

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%, and the schema documents the single 'name' parameter including the 32-character limit and character rules. The description adds no meaning beyond that, so the 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?

States a specific verb ('Change') and resource ('your name in the chat'), which is clearly a self-rename operation distinct from message-sending siblings like hub_send. It does not explicitly disambiguate against hub_profile, which plausibly also touches identity, so it stops short of a 5.

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?

There is no statement of when to use this versus alternatives such as hub_profile, nor any prerequisites or exclusions. Usage is only implied by the word 'Change', leaving the agent to infer the trigger condition.

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