Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_repo_switch

Switch the active manager-owned repository route atomically by supplying a live repo_id from the repository list; paths are rejected.

Instructions

MANAGER OPERATION: atomically switch to one live manager-owned repo_id.

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

Input Schema

NameRequiredDescriptionDefault
repo_idYesRepository id of a live repository route (repo_ followed by 32 lowercase hex characters), taken from the repo_id field of aiworkhub_repo_list. A path is not accepted.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.67
    • addedInput schema / properties / repo_id / description
      Added value: +"Repository id of a live repository route (repo_ followed by 32 lowercase hex characters), taken from the repo_id field of aiworkhub_repo_list. A path is not accepted."
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the mutation-but-non-destructive profile is covered. The description adds 'atomically', which usefully signals all-or-nothing switching, but says nothing about the scope of the switch (session-wide?), whether the prior repo can be restored, or failure behavior.

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 compact sentence with the key constraint ('atomically ... live manager-owned') front-loaded. The 'MANAGER OPERATION:' prefix is a mild categorization tag rather than content, but nothing is padded.

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?

With an output schema present and a fully documented single parameter, the basics are covered. However, for a state-changing switch operation the description does not explain what state changes or how it interacts with neighboring repo tools, leaving an agent to infer the semantics.

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%, including the exact id format and that it must come from aiworkhub_repo_list. The description adds only the 'live manager-owned' qualifier, which is a marginal addition over the schema, so baseline 3 is appropriate.

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 ('switch to') and resource ('repo_id'), qualified as atomic and limited to a live manager-owned repo. It is distinguishable from aiworkhub_repo_current (a read) and aiworkhub_repo_list (enumeration), though it never names those siblings explicitly.

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 the prerequisite that the target must be a live, manager-owned repo_id, but gives no explicit when-to-use vs. when-not-to-use or a pointer to aiworkhub_repo_current / aiworkhub_repo_list for comparison. Usage context is only implied.

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