Skip to main content
Glama

List knowledge stacks

list_knowledge_stacks
Read-onlyIdempotent

Retrieve knowledge stacks, including Next Gen stacks, as JSON up to a set limit for a chosen or active workspace; use it to inventory available stacks before requesting suggestions or stack details.

Instructions

List Knowledge Stacks, including Next Gen stacks. Use optimise_knowledge_stacks for suggestions, and get_studio_entity for one stack. Read-only. Returns JSON items up to limit.

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": "list_knowledge_stacks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows. Integer from 1 to 500. Default 100.
workspaceNoOptional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.3.0
    • addedInput schema / properties / workspace
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.",
      +  "title": "Workspace"
      +}
  2. Changed1 schema field changedv6.2.1
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows. Integer from 1 to 500. Default 100."
  3. Addedv6.1.5

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Read-only' largely restates structured data. The description does add that results are JSON items capped by limit, which is useful for anticipating truncated output, but says nothing about ordering or pagination beyond the cap.

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?

Three short sentences, front-loaded with the resource and scope, then alternatives, then return behavior. No filler or repetition.

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 and rich annotations, the description needn't explain return values, and it covers scope, alternatives and the limit cap. Only minor gaps remain, such as result ordering or whether the list is paginated.

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 description coverage is 100%, with both limit (1-500, default 100) and workspace fully documented in the schema. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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 ('List Knowledge Stacks') and adds scope ('including Next Gen stacks'), which lets an agent distinguish it from get_studio_entity (single stack) and optimise_knowledge_stacks (suggestions) without opening any schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use optimise_knowledge_stacks for suggestions and get_studio_entity for one stack, leaving this tool as the enumeration path. The alternatives and the condition selecting them are named directly.

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