Skip to main content
Glama

Market Brew

List Knowledge Bases

list_knowledge_bases
Read-onlyIdempotent

Use this when the user asks to list Knowledge Bases. Returns only data visible to the linked Market Brew account.

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_bases"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional filters: name (partial match), pageSize, and offset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / query / additionalProperties
      Previous value: -{
      -  "type": [
      -    "string",
      -    "number",
      -    "boolean",
      -    "null"
      -  ]
      -}New value: +false
    • addedInput schema / properties / query / properties
      Added value: +{
      +  "name": {
      +    "maxLength": 254,
      +    "type": "string"
      +  },
      +  "offset": {
      +    "maximum": 1000000,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  "pageSize": {
      +    "maximum": 200,
      +    "minimum": 1,
      +    "type": "integer"
      +  }
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuine value with the data-scope constraint ('only data visible to the linked Market Brew account'), which is an authorization boundary not expressible in annotations. It says nothing about pagination behavior or result ordering, which is the remaining behavioral gap.

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?

Two sentences, zero filler, and the usage trigger is front-loaded ahead of the data-scope caveat. Nothing is redundant or padded.

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 simple, no-required-parameter list tool with rich annotations and full schema coverage, the description covers the trigger and the visibility scope. With no output schema, it should ideally say what a returned item looks like or how pagination/total counts behave, so the agent knows whether to loop with offset.

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% and the nested query object documents name, pageSize and offset with bounds, so the schema does the heavy lifting. The description adds no meaning beyond it — no defaults, no note that name is a partial match, no maximum page size — so the baseline of 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 states a specific verb and resource ('list Knowledge Bases'), which reads clearly against siblings like count_knowledge_bases and get_knowledge_base. It stops short of explicitly naming those siblings to differentiate scope, but the operation itself is unambiguous.

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

Usage Guidelines3/5

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

'Use this when the user asks to list Knowledge Bases' gives a clear trigger condition. However, it offers no exclusions or alternatives, so an agent gets no guidance on when to prefer count_knowledge_bases (count only) or get_knowledge_base (single item) over this list tool.

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