Skip to main content
Glama

Set the default knowledge hub

set_default_knowledge_hub
DestructiveIdempotent

Use this when the user wants a different knowledge hub to be the one campaigns use when they name none. 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": "set_default_knowledge_hub"
  }
}

Input Schema

NameRequiredDescriptionDefault
hubIdYesThe hub campaigns use when they name none.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=true, and openWorldHint=false, so safety traits are covered structurally. The description adds only that the operation is 'Free' (no credit cost) and that the new default replaces the previous fallback via 'different'; it does not say whether the prior default setting is altered elsewhere or what a call returns.

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 front-loaded sentence establishes the use case, and the trailing 'Free.' conveys cost information compactly. The fragment 'Free.' is slightly abrupt but costs almost nothing in length.

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 one-parameter, no-output-schema tool the description covers what changes and when to use it. It omits what happens to the previously default hub and whether the response confirms the change, which an agent might want before mutating global campaign behavior.

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?

There is one required parameter with full schema description coverage, including pattern, length bounds, and an example. The description's phrase 'the one campaigns use when they name none' merely restates the schema's wording rather than adding format or selection guidance, so the baseline 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?

The description names the specific effect: which knowledge hub campaigns fall back to when none is named. That is distinct from create/update/delete_knowledge_hub siblings, though the verb 'set' is only implied by 'Use this when the user wants...' rather than stated as an action.

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?

A concrete trigger condition is given: the user wants a different hub to be the fallback for campaigns that name none. No exclusions or named alternatives are offered, so an agent must infer that update_knowledge_hub is not the right choice for changing the default.

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