Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_manager_kb_get

Read-only

Retrieve an exact active knowledge base entry by key for canonical lookup, avoiding ambiguous matches.

Instructions

MANAGER READ: exact canonical KB entry 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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesExact KB entry key, non-blank, at most 256 bytes; only an active entry is returned.

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 KB entry key, non-blank, at most 256 bytes; only an active entry is returned."
  2. First observedv0.1.0

TDQS

A3.6/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 covered. The description adds 'MANAGER READ' and 'exact canonical' as behavioral clues, but does not explain missing-key behavior or active-entry filtering beyond what the schema already states.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded phrase with no repetition or filler. It is appropriately sized for a single-parameter read tool.

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

Completeness4/5

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

For a simple exact-lookup tool with a fully described schema and an output schema, the description is nearly sufficient. It could be more complete only by explicitly routing agents away from aiworkhub_manager_kb_search, which is a minor gap.

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 'key' parameter is fully documented in the schema. The description adds no parameter syntax or validation details beyond the schema, 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 ('lookup') and resource ('exact canonical KB entry'), with the 'exact' qualifier distinguishing it from fuzzy KB search. It does not name a sibling alternative, so a 4 rather than 5.

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 word 'exact' implies you should only use it when you already have the precise key, but there is no explicit when-not condition or pointer to aiworkhub_manager_kb_search for fuzzy lookup. Guidance 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