Skip to main content
Glama

get_parent_schema

Retrieve the parent UI schema for a given node UID. Input the child's UID to obtain its parent schema.

Instructions

Get the parent UI schema of a node by UID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYesUI schema UID of the child node

Implementation Reference

  • The handler function for get_parent_schema tool. It receives a uid string, calls the NocoBase API endpoint /api/uiSchemas:getParentJsonSchema/{uid}, and returns the result as JSON text content.
      async ({ uid }) => ok(await nocoFetch(`/api/uiSchemas:getParentJsonSchema/${uid}`))
    );
  • Input schema for get_parent_schema. Defines a required 'uid' parameter (string) describing the child node's UID.
    {
      description: "Get the parent UI schema of a node by UID",
      inputSchema: { uid: z.string().describe("UI schema UID of the child node") },
    },
  • src/index.ts:77-84 (registration)
    Registration of the get_parent_schema tool using server.registerTool() with name 'get_parent_schema', description, input schema, and async handler.
    server.registerTool(
      "get_parent_schema",
      {
        description: "Get the parent UI schema of a node by UID",
        inputSchema: { uid: z.string().describe("UI schema UID of the child node") },
      },
      async ({ uid }) => ok(await nocoFetch(`/api/uiSchemas:getParentJsonSchema/${uid}`))
    );
  • src/index.ts:394-401 (registration)
    MANUAL_TOOLS set includes 'get_parent_schema', which prevents the tool from being re-registered from the dynamic OpenAPI/Swagger spec generation.
    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?

With no annotations provided, the description must fully disclose behavioral traits. It does not mention side effects, permissions, error handling (e.g., if UID not found), or whether the tool is read-only.

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, efficient sentence with no unnecessary words. It conveys the essential information concisely.

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?

For a simple getter with one required parameter and no output schema, the description is adequate. It could mention the return value (the parent UI schema) for greater completeness, but is still sufficient.

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?

The input schema already describes the parameter as 'UI schema UID of the child node' (100% coverage). The tool description adds no additional meaning beyond confirming the UID identifies the child node.

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 ('Get'), the resource ('parent UI schema'), and the identifier ('by UID'). It distinguishes this read operation from sibling tools which involve creation, updates, or deletions.

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?

The description provides no guidance on when to use this tool over alternatives, nor does it mention prerequisites or contexts where it should not be used.

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