Skip to main content
Glama
xano-inc

Xano Developer MCP

Official
by xano-inc

xano_xanoscript_docs

Read-onlyIdempotent

Retrieve XanoScript documentation by topic or file path to generate accurate AI code. Use quick reference or tiered summaries to fit context limits.

Instructions

Get XanoScript programming language documentation for AI code generation. Call without parameters for a compact index of all topics (~4KB, ~1K tokens); then drill in with topic= or file_path=. Use topic='readme' for the full prose overview (previously the no-arg default). For context-limited models: use tier='survival' (~1.2K tokens) or tier='working' (~4.5K tokens). Use 'topic' for specific documentation, or 'file_path' for context-aware docs based on the file you're editing. Use mode='quick_reference' for compact syntax reference (recommended for context efficiency). Use max_tokens to limit documentation size to fit your context budget. file_path mode defaults to 'quick_reference' to reduce context size; use mode='full' to get complete docs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo'full' = complete documentation with explanations and examples. 'quick_reference' = compact reference with just syntax patterns and signatures. 'index' = compact topic listing with descriptions and byte sizes (~4KB, ~1K tokens). When set, 'index' takes precedence over topic and file_path. Use 'index' to discover available topics before loading them. Use 'quick_reference' to save context window space when you just need a reminder. Default: 'full' for topic mode, 'quick_reference' for file_path mode.
tierNoPre-packaged documentation tier for context-limited models. 'survival' (~5KB, ~1.2K tokens): minimum syntax to write valid XanoScript. 'working' (~18KB, ~4.5K tokens): complete reference for common tasks. Overrides topic/file_path/mode when set. Use 'survival' for models with <16K context, 'working' for 16-64K context.
topicNoDocumentation topic to retrieve. Call without any parameters to get the compact topic index; use topic='readme' for the full prose overview. Example: topic='syntax' for language syntax, topic='database' for database operations, topic='types' for type system. Common synonyms are accepted and resolved automatically (e.g. 'upload'/'storage' -> 'file-uploads'); an unrecognized topic returns the list of valid topics. Available topics: survival (Minimal syntax survival kit for writing valid XanoScript), working (Complete working reference for common XanoScript tasks), readme (XanoScript overview, workspace structure, and quick reference), essentials (Common patterns, quick reference, and common mistakes to avoid), syntax (Expressions, operators, and filters for all XanoScript code), syntax/string-filters (String filters, regex, encoding, security filters, text functions), syntax/array-filters (Array filters, expression-based higher-order filters (map/filter/reduce), JS lambda filters (lambda_map/lambda_reduce), and array functions), syntax/functions (Math filters/functions, object functions, bitwise operations), types (Data types, input blocks, and validation), tables (Database schema definitions with indexes and relationships), functions (Reusable function stacks with inputs and responses), apis (HTTP endpoint definitions with authentication and CRUD patterns), tasks (Scheduled and cron jobs), triggers (Event-driven handlers (table, realtime, workspace, agent, MCP)), database (All db), agents (AI agent configuration with LLM providers and tools), tools (AI tools for agents and MCP servers), mcp-servers (MCP server definitions exposing tools), unit-testing (Unit tests, mocks, and assertions within functions, APIs, and middleware), workflow-tests (End-to-end workflow tests with data source selection and tags), integrations (External service integrations index - see sub-topics for details), integrations/cloud-storage (AWS S3, Azure Blob, and GCP Storage operations (external buckets, not native Xano storage)), integrations/search (Elasticsearch, OpenSearch, and Algolia search operations), integrations/redis (Redis caching, rate limiting, and queue operations), integrations/external-apis (HTTP requests with api), integrations/utilities (Local storage, email, zip, and Lambda utilities), file-uploads (Uploading files to native Xano storage: file? input, create_attachment, sign_private_url), frontend (Static frontend development and deployment (static hosting)), addons (Reusable subqueries for fetching related data), debugging (Logging, inspecting, and debugging XanoScript execution), performance (Performance optimization best practices), realtime (Real-time channels and events for push updates), security (Security best practices for authentication and authorization), streaming (Streaming data from files, requests, and responses), middleware (Request/response interceptors for functions, queries, tasks, and tools), branch (Branch-level settings: middleware, history retention, visual styling), workspace (Workspace-level settings: environment variables, preferences, realtime)
file_pathNoFile path being edited. Returns all relevant docs automatically based on the file type and location. Uses applyTo pattern matching to select applicable topics. Example: 'api/users/create.xs' returns API, database, and syntax docs. 'function/format.xs' returns function and syntax docs.
max_tokensNoMaximum estimated token budget for documentation. When used with file_path, loads topics in priority order until budget is reached. Helps prevent context overflow for small-window models. Estimate: 1KB of docs ≈ 250 tokens.
exclude_topicsNoList of topic names to exclude from file_path results. Use this to skip topics you've already loaded (e.g., exclude_topics: ['syntax', 'essentials']). Only applies when using file_path parameter.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoThe documentation mode used.
tierNoThe pre-packaged tier used, if any.
topicsNoList of matched topic names (file_path mode only).
versionNoThe XanoScript documentation version.
file_pathNoThe file path that was matched (file_path mode only).
documentationNoThe documentation content (index, topic, tier, or file_path mode).
Behavior5/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, indicating safe read operations. The description adds significant behavioral context: token sizes, parameter overrides (tier overrides topic/file_path/mode), default modes for file_path, and pattern matching for file_path. No contradictions.

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?

The description is efficient and front-loaded with the main purpose, then systematically covers parameters. It is relatively long but every sentence earns its place. Slight improvement could be bullet points for parameter details, but it is still well-structured.

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 6 interdependent parameters and no required ones, the description comprehensively covers all usage scenarios: context limits, token budgets, default behaviors, and parameter priorities. Output schema exists, so return values are documented elsewhere.

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?

Schema description coverage is 100%, so baseline is 3. The description enriches beyond schema by explaining interactions (e.g., tier overrides), giving examples (topic='readme' default change), and detailing context budget strategies. It adds substantial value.

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 the tool's purpose: 'Get XanoScript programming language documentation for AI code generation.' It uses a specific verb and resource, and distinguishes it from sibling tools like xano_cli_docs and xano_meta_api_docs by focusing on XanoScript documentation.

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?

The description provides explicit guidance on when to use each parameter: call without parameters for index, use topic, file_path, tier, mode, max_tokens, exclude_topics. It explains context considerations and default behaviors, and implicitly indicates alternatives (sibling tools for other docs).

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