Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_manager_kb_related

Read-only

Finds knowledge base entries related to an exact key by shared tag or recorded link, so you can trace connected notes and dependencies.

Instructions

MANAGER READ: bounded canonical KB relation lookup.

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

Input Schema

NameRequiredDescriptionDefault
keyYesExact key of the KB entry to find related entries for, non-blank, at most 256 bytes; related means a shared tag or a recorded link.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.67
    • addedInput schema / properties / key / description
      Added value: +"Exact key of the KB entry to find related entries for, non-blank, at most 256 bytes; related means a shared tag or a recorded link."
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is clear. The description adds 'bounded canonical' which hints at a limited result set but does not specify limits or behavior beyond that; with annotations carrying the main disclosure burden, a 3 is appropriate.

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 with no wasted words. However, the 'MANAGER READ' prefix and 'canonical' add jargon that could be trimmed or clarified, keeping it from a perfect 5.

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 one-parameter read-only tool with an output schema, the description is minimally adequate. It omits any mention of result limits or how 'related' is defined (though the schema covers that), and provides no usage context relative to siblings, leaving some gaps.

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 single parameter is fully documented in the schema. The description adds no parameter-level detail, so it meets the baseline of 3 for high schema coverage.

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?

The description states a specific verb ('relation lookup') and resource ('KB'), making it clear the tool finds entries related to a given key. It does not explicitly differentiate from sibling tools like kb_search or kb_get, so it falls 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 guidance on when to use this tool versus alternatives (e.g., kb_search, kb_get, context_graph_related). The description only asserts what it does, leaving the agent to infer appropriate usage from the tool name alone.

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