Skip to main content
Glama

create_page

Create a new root-level UI page schema in NocoBase by providing a JSON schema object.

Instructions

Create a new root-level UI schema node in NocoBase

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schemaYesUI schema object to create (JSON)

Implementation Reference

  • src/index.ts:86-95 (registration)
    Registration of the 'create_page' tool via server.registerTool, with inputSchema describing a JSON schema object and a handler that POSTs to /api/uiSchemas.
    // 7. create_page
    server.registerTool(
      "create_page",
      {
        description: "Create a new root-level UI schema node in NocoBase",
        inputSchema: { schema: JsonObject.describe("UI schema object to create (JSON)") },
      },
      async ({ schema }) =>
        ok(await nocoFetch("/api/uiSchemas", { method: "POST", body: JSON.stringify(schema) }))
    );
  • The handler for 'create_page' is an inline async function that takes a 'schema' parameter and calls nocoFetch('/api/uiSchemas', { method: 'POST', body: JSON.stringify(schema) }).
    // 7. create_page
    server.registerTool(
      "create_page",
      {
        description: "Create a new root-level UI schema node in NocoBase",
        inputSchema: { schema: JsonObject.describe("UI schema object to create (JSON)") },
      },
      async ({ schema }) =>
        ok(await nocoFetch("/api/uiSchemas", { method: "POST", body: JSON.stringify(schema) }))
    );
  • Input schema for 'create_page' uses a reusable JsonObject (z.record(z.string(), z.unknown())) described as 'UI schema object to create (JSON)'.
    {
      description: "Create a new root-level UI schema node in NocoBase",
      inputSchema: { schema: JsonObject.describe("UI schema object to create (JSON)") },
  • The MANUAL_TOOLS set includes 'create_page' to prevent it from being re-registered by the dynamic OpenAPI tool loader.
    const MANUAL_TOOLS = new Set([
      "list_collections","get_collection","list_pages","get_page",
      "get_parent_schema","create_page","insert_new_schema","insert_adjacent_schema",
      "update_ui_schema","batch_patch_ui_schema","remove_ui_schema","save_as_template",
      "list_desktop_routes","get_flow_model","get_flow_model_by_parent","save_flow_model",
      "attach_flow_model","move_flow_model","duplicate_flow_model","destroy_flow_model",
      "get_js_block","update_js_block",
    ]);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It merely says 'create' without disclosing side effects, permissions, or behavior if the schema already exists. For a mutation tool, this is insufficient.

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 a single concise sentence with no wasted words. It is front-loaded with the verb and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has a complex nested parameter and no output schema, the description lacks details about return values, success indicators, or how the schema relates to existing pages. It leaves the agent guessing.

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%, so baseline is 3. The description adds no extra meaning beyond the schema's 'UI schema object to create (JSON)'. No parameter documentation beyond that.

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 action (create) and resource (root-level UI schema node) and system (NocoBase). It distinguishes from siblings like 'update_ui_schema' by specifying 'root-level'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'insert_new_schema' or 'insert_adjacent_schema'. The description does not mention prerequisites or context.

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