Skip to main content
Glama
Sign In
crewchat

crewchat

by deepankar17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

hub_role

Idempotent

Set an AI agent's owner-assigned role, or retrieve the role's instructions when no role is provided.

Instructions

Take a role your owner gives you; with none, see your role's instructions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hub_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNolead, developer, qa, docs, reviewer, the owner's own, or none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / role / description
      Previous value: -"lead, developer, qa, docs, reviewer, a role your owner defined, or 'none' to drop yours."New value: +"lead, developer, qa, docs, reviewer, the owner's own, or none."
  2. Changed1 schema field changedv0.13.4
    • changedInput schema / properties / role / description
      Previous value: -"The role's name, or 'none'."New value: +"lead, developer, qa, docs, reviewer, a role your owner defined, or 'none' to drop yours."
  3. First observedv0.9.5

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, idempotent write (readOnlyHint=false), so the safety profile is covered. The description contributes the dual-mode behavior (pass a role to assume it, pass none to read instructions) and implies owner-granted authority, but it omits what changes on assignment, whether it persists across calls, and what a successful call returns.

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 no filler and the mode-switch condition placed up front. It is efficiently sized; the problem is density of meaning, not length.

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

Completeness2/5

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

With no output schema and no annotations describing effects, the description must explain what an agent gets back from each branch. It does not: the effect of assigning a role, the shape of the returned instructions, and persistence of the choice are all unstated for a tool operating on a multi-agent hub.

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% and the single optional parameter is fully enumerated in the schema, so the baseline is 3. The description adds one piece of meaning — that the "none" value yields the current role's instructions — but says nothing about the allowed values beyond what the schema lists.

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

Purpose2/5

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

"Take a role" plus the "none" clause gestures at a role-assignment operation, but the sentence is a fragment that never states what the tool actually does — whether it sets the calling agent's persona, switches permissions, or simply retrieves instructions. It also does not distinguish itself from siblings such as hub_profile or hub_status, which plausibly overlap.

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?

The only guidance is the conditional "with none, see your role's instructions," which explains one parameter branch but not when to call the tool at all or why to choose it over hub_profile. No alternatives or preconditions are named.

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