Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_repo_list

Read-only

Lists live repository identities available to this manager, showing which repos are connected. Optionally include inactive routes or cap results; read-only.

Instructions

READ-ONLY: bounded live repository identities available to this manager.

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": "aiworkhub_repo_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum registry records to read, newest first; default 64, clamped to 1-256.
include_inactiveNoTrue also lists routes whose extension host is not alive or is stale; default false keeps only live routes and the current repository (the rest are summarized under inactive).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.67
    • addedInput schema / properties / include_inactive / description
      Added value: +"True also lists routes whose extension host is not alive or is stale; default false keeps only live routes and the current repository (the rest are summarized under inactive)."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum registry records to read, newest first; default 64, clamped to 1-256."
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

The description repeats the read-only nature already declared by annotations and adds 'bounded live', which is useful context about scope. However, it does not disclose return format, pagination behavior beyond the schema's limit, or how inactive routes are summarized, so it adds limited value beyond structured data.

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?

The description is a single front-loaded sentence that avoids waste and immediately signals read-only status. Given the rich schema, this compact form is appropriate, though it could be slightly more explicit about the listing action.

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 simple two-parameter read-only tool with full schema coverage and an output schema, the description is minimally complete but omits sibling differentiation. An agent can likely invoke it correctly from the schema alone, but the purpose remains slightly ambiguous without knowing how it relates to repo_current and repo_switch.

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 both parameters (limit, include_inactive) are fully documented, so the description is not needed to explain parameter semantics. The description adds no parameter-specific meaning beyond what the schema already provides.

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

Purpose3/5

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

The description states the resource ('repository identities') and a scope ('bounded live', 'available to this manager'), but it lacks a clear verb and never explicitly says it lists repositories. It also does not distinguish this listing from siblings like aiworkhub_repo_current or aiworkhub_repo_switch, leaving the agent to infer the action.

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?

No guidance is provided on when to use this tool versus alternatives such as aiworkhub_repo_current or aiworkhub_repo_switch. The phrase 'available to this manager' hints at a broad listing, but it is not framed as a selection criterion and no exclusions are stated.

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