Skip to main content
Glama
xano-inc

Xano Developer MCP

Official
by xano-inc

xano_knowledge_get

Read-onlyIdempotent

Retrieve the CLI command to obtain the full content of a knowledge item or its attached reference file. Use after listing items to access detailed documentation.

Instructions

Get the CLI command to fetch the full content of one named knowledge item (a skill, doc, or agents.md), or one of a skill's attached reference files. This tool does not run the command itself — it returns the exact xano knowledge get command to run in a shell, so you can invoke it and read its output.

Use this after xano_knowledge_list has identified an on-demand item whose full content is now needed, or when a skill's step tells you to consult a specific reference file (via @filename syntax in the skill content).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNoPath of a reference file attached to the item (as listed in that item's `references` array from xano_knowledge_list), fetched instead of the item's own content.
nameYesThe knowledge item's name (case-insensitive exact match). Required.
branchNoBranch ID. Optional; defaults to the workspace's live branch.
outputNotext returns the raw markdown content. json wraps it with metadata (item: full object; file: {content, name, path}). Default: text.
profileNoCLI credential profile to use.
workspaceNoWorkspace ID. Optional if the active profile has a default workspace configured.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesThe `xano knowledge get` command to run to fetch the knowledge item's content.
Behavior5/5

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

Description discloses key behavioral trait beyond annotations: 'This tool does not run the command itself — it returns the exact xano knowledge get command to run in a shell'. This adds value over readOnlyHint and idempotentHint.

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 concise paragraphs, front-loaded with purpose and behavior, followed by usage context. No unnecessary words.

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?

Output schema exists, description needn't detail return values. It covers what is returned (CLI command), when to use, and relation to xano_knowledge_list. Complete for this tool's complexity.

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 coverage is 100%, so baseline 3 is appropriate. Description adds little beyond schema descriptions, only noting the purpose of 'name' and reference files already covered in schema.

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 fetch content of a knowledge item (skill, doc, agents.md) or reference file. It distinguishes from siblings by noting it does not run the command itself and positions itself after xano_knowledge_list.

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?

Explicitly states when to use: after xano_knowledge_list identifies an item or when a skill step references a file. Implicitly excludes direct execution. Could add explicit 'when not to use' but context is clear.

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