Skip to main content
Glama

Rewrite a hub's page

regenerate_knowledge_hub_page
Destructive

Use this when the user wants one knowledge hub page written again from the hub's sources, replacing its current content. A page added by hand has no sources and is refused. It can take a minute. 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>",
      "pageId": "<pageId>"
    },
    "name": "regenerate_knowledge_hub_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
hubIdYesThe knowledge hub's id.
pageIdYesThe page's id, as the hub's pages list gives it.

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 destructiveHint=true and readOnlyHint=false, and the description reinforces this by saying current content is replaced. It adds genuinely new behavioral context: a precondition that fails for hand-added pages, an expected duration ('can take a minute'), and a cost signal ('Free'). It does not address auth/permissions or what the regenerated page looks like on return.

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?

Four short sentences, front-loaded with the trigger condition, each carrying distinct information: trigger, refusal precondition, latency, cost. Nothing is redundant.

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

Completeness5/5

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

For a two-parameter mutation with no output schema and annotations that already cover the safety profile, the description supplies everything an agent needs: what is replaced, when the call fails, how long it takes, and that it is free.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters are fully documented in the schema, including patterns and the hint that pageId comes from the hub's pages list. The description adds no meaning about either parameter, not even that both must belong to the same hub — though the schema's 100% coverage keeps this from being a serious gap.

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?

The description states a specific verb and resource ('one knowledge hub page written again') plus the mechanism ('from the hub's sources') and the effect ('replacing its current content'). That mechanism distinguishes it from update_knowledge_hub_page, which would be a manual edit, without needing to name the sibling.

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?

It gives an explicit trigger ('Use this when the user wants one knowledge hub page written again') and an explicit refusal case ('A page added by hand has no sources and is refused'). It stops short of naming a sibling alternative for cases where a hand edit is what the user actually wants.

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