Skip to main content
Glama
Stellify-Software-Ltd

Stellify MCP Server

Official

create_route

Create a route or page in a Stellify project. API routes require both controller and controller_method UUIDs to execute code.

Instructions

Create a route/page. For API routes, you MUST pass BOTH controller AND controller_method UUIDs to wire execution.

IMPORTANT: Both 'controller' (file UUID) and 'controller_method' (method UUID) are required together for API routes to execute code. Without both, the route won't run any code.

Route params like {id} auto-inject into controller method parameters when names match.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesThe UUID of the Stellify project
nameYesRoute/page name (e.g., "Home", "Counter", "notes.index")
pathYesURL path (e.g., "/", "/counter", "/api/notes")
methodYesHTTP methodGET
typeNoRoute type: "web" for pages, "api" for API endpoints, "channels" for WebSocket channels, "view" for Blade viewsweb
controllerNoUUID of the controller file. MUST be provided together with controller_method for API routes to execute code.
controller_methodNoUUID of the method to execute. MUST be provided together with controller for API routes to execute code.
dataNoAdditional route data (title, description, element UUIDs)
moduleNoOptional module name to group this route with related code (e.g., "blog-posts", "user-auth"). Module is auto-created if it doesn't exist.
Behavior5/5

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

Without annotations, the description fully discloses critical behavior: that without both controller fields, the route won't execute any code. It also explains the auto-injection behavior, leaving no hidden surprises.

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?

Well-structured with three concise paragraphs: purpose, critical requirement, and a helpful detail about route params. No extraneous information; every sentence adds value.

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 9 parameters (4 required) and no output schema, the description covers key behavioral aspects. However, it could mention default behavior for web routes or what happens if controller_method is provided without controller, but overall it is sufficiently complete.

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 provides 100% coverage with descriptions, but the description adds significant value by clarifying the dependency between controller and controller_method and explaining how route params map to method parameters, going beyond schema details.

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 creates a route/page, distinguishes between regular routes and API routes requiring both controller and controller_method, and contrasts with sibling tools like delete_route or save_route.

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?

Explicitly instructs that for API routes, both 'controller' and 'controller_method' UUIDs are required. Also explains automatic injection of route params like {id} into method parameters, providing clear when-to-use 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/Stellify-Software-Ltd/stellify-mcp'

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