Skip to main content
Glama
Stellify-Software-Ltd

Stellify MCP Server

Official

analyze_attributes

Analyze PHP 8 attribute usage in Stellify projects. List all attributes, find missing attributes, or search for specific attribute values to audit and debug.

Instructions

Analyze PHP 8 attribute usage across a Stellify project. Useful for auditing, finding missing attributes, and searching attribute values.

Three modes:

  1. usage (default): List all attributes used in the project with counts

    • Optional: file_type to filter (e.g., "model", "controller")

    • Returns: attribute names, counts, and files using each

  2. missing: Find files of a specific type missing a required attribute

    • Required: file_type (e.g., "model", "class")

    • Required: attribute name (e.g., "Fillable", "FailOnUnknownFields")

    • Returns: files missing vs having the attribute

  3. search: Find files where an attribute contains a specific value

    • Required: attribute name

    • Optional: value to search for in attribute args

    • Optional: file_type to filter

    • Returns: matching files with their attribute values

Example queries:

  • "Find every FormRequest missing FailOnUnknownFields": mode=missing, file_type=class, attribute=FailOnUnknownFields

  • "Find models where 'email' is fillable": mode=search, attribute=Fillable, value=email

  • "List all attributes used": mode=usage

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoAnalysis mode: "usage" (list all attributes), "missing" (find files missing an attribute), "search" (find files with specific attribute value). Default: usage.
file_typeNoFilter by file type (e.g., "model", "controller", "class", "middleware").
attributeNoAttribute name to analyze (required for "missing" and "search" modes).
valueNoValue to search for in attribute arguments (for "search" mode).
Behavior3/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 explains modes and outputs but does not explicitly state that the tool is read-only or mention any side effects, rate limits, or security requirements. While analysis suggests no destructive behavior, the description lacks explicit transparency.

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 well-structured with clear headings for each mode, bullet points for outputs, and inline examples. It is information-dense yet concise, with no fluff or redundant sentences. Every sentence serves a purpose.

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

Completeness5/5

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

Given the complexity (3 modes, 4 params) and no output schema, the description thoroughly covers all return values per mode, parameter dependencies, and provides example queries. It is complete enough for an agent to correctly invoke the tool in various use cases.

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?

All 4 parameters have schema descriptions (100% coverage). The description adds substantial value by explaining which parameters are required per mode, how they interact, and providing concrete examples of values (e.g., 'Fillable', 'email'). This goes well beyond the schema.

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 analyzes PHP 8 attribute usage across a Stellify project. It defines three distinct modes with specific purposes and provides example queries, making the tool's purpose unambiguous and distinguishable from siblings like search_attributes.

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 explicitly details when to use each mode and gives example mappings from natural language to parameters. However, it does not compare against sibling tools or specify when not to use this tool, missing a chance to fully differentiate from search_attributes.

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