Skip to main content
Glama
maschmann

symfony-php-mcp

by maschmann

find_symbol

Search the symbol index to locate PHP classes, interfaces, traits, enums, or methods by name. Returns file paths and line numbers for direct code access.

Instructions

Search the symbol index for a PHP class, interface, trait, enum, or method.

Returns file paths and line numbers — use the result directly with read_code_context to inspect the implementation.

Requires build_index to have been run at least once.

Args: name: Name to search for (case-insensitive substring or full name). Examples: "UserController", "UserRepo", "findByEmail", "App\Entity" kind: Optional filter. One of: class, interface, trait, enum, method. Empty = search all symbol types.

Typical workflow:

  1. build_index — index the project (once, or after big changes)

  2. find_symbol "Foo" — locate the file and line

  3. read_code_context — read the file for full implementation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
kindNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description fully discloses behavior: case-insensitive search, optional kind filter, and return of file paths and line numbers. No hidden side effects.

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 a brief purpose sentence, parameter explanations, and a clear workflow. Every sentence adds value, no redundancy.

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?

Covers prerequisites, parameters, and workflow. Output format is mentioned but not detailed; however, an output schema exists to fill that gap.

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?

0% schema coverage, but description adds detailed meaning: 'name' is case-insensitive substring with examples; 'kind' lists allowed values and default behavior. Crucial beyond 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 searches for PHP symbols (class, interface, trait, enum, method) and returns file paths and line numbers, distinguishing it from siblings like search_code.

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?

Explicitly mentions prerequisite (build_index) and provides a typical workflow. Lacks explicit alternatives or when-not-to-use, but context is clear.

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/maschmann/symfony-php-mcp'

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