Skip to main content
Glama
Stellify-Software-Ltd

Stellify MCP Server

Official

create_method

Create a method in a file with optional visibility, static, async, return type, parameters, and body. Includes context fields for summary, rationale, and references.

Instructions

Create a method in a file. Pass 'body' to include implementation. Async auto-detected from await. For significant methods, include context fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesUUID of the file to add the method to
nameYesMethod name (e.g., "increment", "store", "handleClick")
visibilityNoMethod visibility (PHP only)
is_staticNoStatic method (PHP only)
is_asyncNoAsync method (JS/Vue). Auto-detected if body contains await.
returnTypeNoReturn type (e.g., "int", "string", "void", "object")
nullableNoNullable return type (e.g., ?object)
parametersNoMethod parameters (created as clauses). Include datatype for TypeScript annotations.
bodyNoMethod body code. Auto-parses statements.
summaryNoContext: What this method does
rationaleNoContext: Why built this way
referencesNoContext: Related entities [{uuid, type, relationship, note}]
decisionsNoContext: Design decisions
attributesNoPHP 8 attributes for the method (e.g., ["Route(\"/api/users\")"], ["Middleware(\"auth\")"]). Use search_attributes tool to find available attributes.
Behavior3/5

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

With no annotations provided, the description must disclose behavioral traits. It mentions async auto-detection and suggests including context for significant methods, but it does not cover what happens on conflict, required permissions, return values, or side effects. Adequate but incomplete for a 14-parameter mutation tool.

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?

Three sentences, front-loaded with the core purpose. Every sentence adds value: 'Create a method in a file' (purpose), 'Pass body to include implementation' (key param), 'Async auto-detected...' (behavioral hint). No unnecessary words.

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?

Despite 14 parameters, no output schema, and sibling tools like 'add_method_body' and 'save_method', the description fails to explain the relationship between these tools or the full lifecycle. It does not mention that 'create_method' might create a stub and that 'add_method_body' is for adding body later, leading to potential confusion.

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 coverage is 100%, so baseline is 3. The description adds marginal value by explaining when to use 'body' (to include implementation) and the auto-detection of 'is_async', but these are minor additions. It does not explain the context fields in detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action is to create a method in a file and mentions key aspects like passing body and async detection. It is specific enough to differentiate from broader tools like 'create_statement', though it does not explicitly name alternatives.

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 gives some guidance on when to include body and context fields, but it does not provide any guidance on when to use this tool versus siblings like 'add_method_body' or 'save_method'. No exclusions or when-not-to-use information is given.

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