Skip to main content
Glama

Optimise knowledge stacks

optimise_knowledge_stacks
Read-onlyIdempotent

Generate read-only JSON suggestions for Knowledge Stack changes based on live Studio Next Gen, draft, and compose status. Use it to plan stack optimizations without editing them.

Instructions

Suggest Knowledge Stack changes from live Studio Next Gen, draft and compose status. Does not edit stacks. Use list_knowledge_stacks to browse them. Read-only. Returns JSON suggestions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "optimise_knowledge_stacks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv5.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so 'Read-only' and 'Does not edit stacks' largely restate structured data. The description does add that the output is advisory JSON suggestions rather than applied changes, which is useful, but nothing about how suggestions are derived or their scope.

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 front-loaded sentences, all relevant. There is minor redundancy between 'Does not edit stacks' and 'Read-only', which could be merged without losing meaning.

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 an output schema present, the description need not explain return values, and it correctly signals that output is advisory suggestions. The only gap is the undefined 'live / draft / compose status' terminology, which affects whether an agent knows for which stacks suggestions are produced.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 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 states a specific verb (suggest changes) and resource (Knowledge Stacks), and distinguishes itself from list_knowledge_stacks by naming the browse alternative. However, the phrase 'from live Studio Next Gen, draft and compose status' is unexplained jargon, so the scope of what is analysed is not fully clear.

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 explicitly routes the agent: 'Use list_knowledge_stacks to browse them', separating read/browse from suggest/optimise. It does not state preconditions (e.g. whether a stack must exist or be in a particular status), so it stops short of full when/when-not guidance.

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