Skip to main content
Glama

list_pages

List all UI schemas in NocoBase, returning raw schema nodes for direct access to the schema structure, not page-level navigation.

Instructions

List all UI schemas in NocoBase (returns raw schema nodes, not page-level navigation)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function that executes the 'list_pages' tool logic by calling nocoFetch('/api/uiSchemas') and formatting the result via ok().
    async () => ok(await nocoFetch("/api/uiSchemas"))
  • The description/inputSchema for list_pages (no input parameters defined).
    { description: "List all UI schemas in NocoBase (returns raw schema nodes, not page-level navigation)" },
  • src/index.ts:60-64 (registration)
    Registration of the 'list_pages' tool via server.registerTool() with name, description, and handler.
    server.registerTool(
      "list_pages",
      { description: "List all UI schemas in NocoBase (returns raw schema nodes, not page-level navigation)" },
      async () => ok(await nocoFetch("/api/uiSchemas"))
    );
  • The nocoFetch helper used by the handler to make HTTP requests to the NocoBase API.
    async function nocoFetch(path: string, options: RequestInit = {}): Promise<unknown> {
      const url = `${NOCOBASE_URL}${path}`;
      const res = await fetch(url, {
        ...options,
        headers: { ...reqHeaders, ...(options.headers as Record<string, string> | undefined) },
      });
      const text = await res.text();
      if (!res.ok) throw new Error(`HTTP ${res.status} ${res.statusText}: ${text}`);
      try { return JSON.parse(text); } catch { return text; }
    }
  • The ok helper used by the handler to wrap results in MCP content format.
    const ok = (data: unknown) => ({
      content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }],
    });
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It reveals the return type (raw schema nodes) and that it returns all schemas, but lacks details on side effects, permissions, rate limits, or error behavior. It is adequate but not comprehensive.

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 extremely concise: two sentences, no wasted words. The first sentence states the main purpose, the second clarifies the output type. Perfectly front-loaded.

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?

Given no output schema and no annotations, the description adequately covers what the tool does and returns. It specifies 'all UI schemas' and 'raw schema nodes'. However, it could mention if there are any limitations (e.g., pagination) or error scenarios. Overall, it is mostly complete for a simple listing tool.

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

Parameters4/5

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

With zero parameters and 100% schema coverage, the baseline is 4. The description does not need to add parameter info, and it does not. It accurately conveys that no inputs are needed.

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 lists all UI schemas in NocoBase, using specific verb ('list') and resource ('UI schemas'). It also clarifies that it returns raw schema nodes, not page-level navigation, distinguishing it from siblings like get_page.

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?

The description implicitly suggests when to use this tool (getting raw schema nodes) vs siblings (e.g., get_page for a specific page). However, it does not explicitly state when not to use or provide alternatives, missing the chance to offer stronger guidance.

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/puguhsudarma/nocobase-mcp-server'

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