Skip to main content
Glama

Read a hub's website again

refresh_knowledge_hub
Destructive

Use this when one of a knowledge hub's websites has changed and its pages should catch up. Reads that website again in the background and rewrites the pages that draw on it. The site must be one the hub already has. 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>",
      "url": "<url>"
    },
    "name": "refresh_knowledge_hub"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesOne of the hub's sites, as its `websites` list it.
hubIdYesThe knowledge hub's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so the bar is lower, but the description still adds real context: the work happens in the background, existing pages that draw on the site get rewritten (spelling out what the destruction is), the site must already exist in the hub, and the call costs nothing. What is missing is how to observe completion or failure for an asynchronous job, which matters given the cancel_job sibling.

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?

Four short sentences lead with the when-to-use condition, then the effect, then the prerequisite, then cost. The one-word "Free." fragment is justified because it carries cost information an agent would otherwise lack; nothing else is padded.

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 two-parameter, destructive, asynchronous operation with no output schema, the definition covers the trigger, the side effect, the prerequisite and the cost. The main remaining gap is that it never says how an agent learns the background refresh finished, which for an async job is a notable omission.

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 both parameters are already documented, including that url must be one of the hub's listed sites. The description's constraint statement largely restates the schema's "One of the hub's sites, as its `websites` list it" and adds no format or identity detail beyond it, so 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?

The description gives a specific verb and resource: it re-reads one of a hub's websites and rewrites the pages that depend on it. That clearly separates a site-level refresh from the page-level sibling regenerate_knowledge_hub_page, though it never names that sibling outright.

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 one of a knowledge hub's websites has changed and its pages should catch up" states the trigger condition precisely, and "The site must be one the hub already has" adds a hard prerequisite. It stops short of naming when NOT to use it, e.g. re-reading a single page instead of the whole site.

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