Skip to main content
Glama
xano-inc

Xano Developer MCP

Official
by xano-inc

xano_knowledge_list

Read-onlyIdempotent

Return the CLI command to list a Xano workspace's knowledge base (skills, docs, agents.md). Review existing knowledge before adding new items to prevent duplicates.

Instructions

Get the CLI command to list a Xano workspace's knowledge base: skills, docs, and the agents.md file. This tool does not run the command itself — it returns the exact xano knowledge list command to run in a shell, so you can invoke it and read its output.

Use this to get an overview of what knowledge/skills exist before answering questions about workspace conventions, or before deciding whether a new skill/doc needs to be created (to avoid duplicating existing ones).

Always-on items (mode=always) are returned by the command with full content; on-demand items are returned with just name+description — use xano_knowledge_get to get the command for fetching an on-demand item's full content when it becomes relevant.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter to a single knowledge type. Omit to list all types.
branchNoBranch ID to read knowledge from. Optional; defaults to the workspace's live branch.
outputNomarkdown is human-readable (always-on items inline, on-demand items as a name+description index). json returns the full raw item array — prefer json when you need structured fields (id, guid, mode, references, etc.) for further processing. Default: markdown.
profileNoCLI credential profile to use. Optional; falls back to XANO_PROFILE env var or the credentials file default.
workspaceNoWorkspace ID. Optional if the active profile has a default workspace configured.
enabled_onlyNoWhen true (default), only enabled items are returned. Set to false to include disabled items too.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesThe `xano knowledge list` command to run to get the workspace's knowledge base.
Behavior5/5

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

The description clearly discloses that the tool does not run the command but returns it for shell execution. It also explains the command's output behavior (always-on items with full content, on-demand with name+description). Annotations (readOnlyHint, idempotentHint) are consistent and reinforced.

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?

The description is three paragraphs with clear front-loading: first sentence states the core action, second clarifies a key nuance, third provides usage guidance. Every sentence is informative and non-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?

Given the simple scope (returning a command string) and presence of an output schema, the description fully covers what the tool does, how its output relates to sibling tools, and the nuances of the underlying command. No gaps remain.

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

Parameters5/5

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

With 100% schema coverage, the description still adds value by explaining the purpose of output format options (markdown vs json) and the enabled_only parameter. It provides context on when to use each format, enhancing the schema's descriptions.

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 clearly states it returns the CLI command to list a Xano workspace's knowledge base, specifying the verb (get), resource (CLI command), and distinguishing it from actual execution. It also mentions the knowledge types (skills, docs, agents.md) and differentiates from sibling xano_knowledge_get.

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?

Explicit usage guidance is provided: use to get an overview before answering questions or creating new knowledge. It also gives when-not-to-use by directing to xano_knowledge_get for on-demand items needing full content.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/xano-inc/xano-developer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server