Skip to main content
Glama
maschmann

symfony-php-mcp

by maschmann

list_services

List Symfony service definitions in YAML mode (fast, reads config/services.yaml) or container debug mode (runs debug:container for compiled services). Filter by pattern and see service ID, class, public flag, and tags.

Instructions

List Symfony service definitions.

Two modes:

  1. YAML mode (default, fast, no PHP required): Reads config/services.yaml directly. Shows explicitly defined services.

  2. Container debug mode (use_container_debug=true): Runs php bin/console debug:container --format=json. Shows the full compiled container including auto-wired services – useful for finding framework/bundle services.

Args: filter_pattern: Regex or substring to filter service IDs or class names. Examples: "App\Service", "mailer", "doctrine" Empty = show all defined services. use_container_debug: Set to true to query the full compiled DI container. Requires PHP and bin/console to be accessible.

Returns a Markdown table with: service ID, class, public flag, tags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filter_patternNo
use_container_debugNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses modes, prerequisites, and return format (Markdown table). Performance characteristics are mentioned, but no explicit statement about non-destructiveness or 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 clear headings, concise yet informative. No unnecessary words; each sentence adds value.

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?

For a tool with 2 optional parameters and an output schema, the description covers usage, modes, filter syntax, and result format completely. No gaps.

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 has 0% coverage (no parameter descriptions), but the tool description thoroughly explains both parameters, including examples and behavior for default values. Highly compensates for missing schema info.

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 lists Symfony service definitions, specifying two modes. The verb 'list' and resource 'service definitions' are explicit. Distinguishes from sibling tools (e.g., find_route, search_code) by domain focus.

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?

Provides detailed guidance on when to use each mode (YAML vs container debug) with prerequisites. However, no explicit comparison to alternative sibling tools, though context makes it less necessary.

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