Skip to main content
Glama

Get a knowledge hub

get_knowledge_hub
Read-only

Use this when you need one knowledge hub's state: its status, its websites with when each was last read, and its notes. It does not return the pages written from them. Free.

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": {
      "hubId": "<hubId>"
    },
    "name": "get_knowledge_hub"
  }
}

Input Schema

NameRequiredDescriptionDefault
hubIdYesThe knowledge hub's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint true and non-destructive, so the description does not need to argue safety. It adds value by disclosing the return payload shape and, notably, that the call is 'Free' (no credit cost), which is not derivable from annotations.

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?

Two sentences, both earning their place: the first covers what comes back, the second covers the exclusion and the cost. Front-loaded with the usage trigger and free of filler.

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?

With no output schema, the description compensates by enumerating the returned fields and the one notable omission, and it adds the cost signal. Only minor gaps remain, such as error behavior for an unknown hubId.

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?

Only one parameter (hubId) at 100% schema coverage with a pattern and length constraint documented, so the schema carries the semantics fully. The description adds no format or constraint detail beyond it, matching the baseline for high-coverage schemas.

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

Purpose5/5

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

States a specific verb and resource ('get one knowledge hub's state') and immediately enumerates the returned contents (status, websites with last-read timestamps, notes). The explicit exclusion 'does not return the pages written from them' cleanly separates it from the page-listing siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use this when you need one knowledge hub's state' gives a clear trigger condition, and the negative clause tells the agent when this tool is not the right source for page content. It stops short of naming the alternative tool (e.g. list_knowledge_hub_pages), leaving the substitution implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources