symfony-agent-mcp

deactivate_category

Free up context budget by removing an activated category from the current session. Deactivate categories when switching between different areas of the Symfony codebase.

Instructions

Remove a previously activated category from this session to free up context budget. Useful when switching between different areas of the codebase.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>"
    },
    "name": "deactivate_category"
  }
}

Input Schema

Name	Required	Description	Default
`category`	Yes	Category key to deactivate, e.g. "database".

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 22, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It adds useful behavioral context by noting the session scoping and the context-budget effect. However, it does not disclose behavior for edge cases like deactivating a category that is not active, or whether the operation is reversible.

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?

Two concise sentences with no filler. The primary action and its purpose are front-loaded, and the use-case guidance is directly relevant.

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?

For a simple one-parameter, session-scoped tool, the description covers what it does, why it matters, and when to use it. It does not mention listing available categories, but the sibling tool list_tool_categories is available in context, making this a minor gap.

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 description coverage is 100%, and the schema already documents the 'category' parameter with an example. The description reinforces the meaning by referring to 'previously activated category' but adds no new parameter-level details 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?

States a specific verb ('Remove'), a specific resource ('previously activated category'), and the scope ('from this session'). It clearly distinguishes the tool from its sibling activate_category by describing the inverse operation.

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 a clear use case: 'Useful when switching between different areas of the codebase.' It implies when to use the tool, though it does not explicitly name alternatives or state when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server