symfony-agent-mcp

activate_category

Enable all tools in a chosen category for the session by passing its category key. Refresh the tools list to receive full definitions; use force=true to override token budget warnings.

Instructions

Activate all tools in a category for this session. After activation the MCP client will receive the full tool definitions on the next tools/list refresh. Use list_tool_categories to see available categories and their token costs. Pass force=true to override the token budget guard.

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": "activate_category"
  }
}

Input Schema

Name	Required	Description	Default
`force`	No	Override token budget warning and activate anyway (default false).
`category`	Yes	Category key from list_tool_categories, e.g. "database", "api", "security".

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 22, 2026

TDQS

A4.6/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the side effect (client receives full tool definitions on next refresh), the session scope, and the token budget guard behavior. It does not mention whether activation is reversible or if there are any side effects beyond the refresh, but the key behaviors are covered.

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, each earning its place: the action and effect, the prerequisite listing tool, and the force parameter. Front-loaded with the primary action, no fluff.

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?

Given the tool's moderate complexity (2 params, no output schema), the description is complete for an agent to call it correctly. It covers the action, the prerequisite, the parameter semantics, and the side effect. The only minor gap is not describing what happens after activation (e.g., whether tools are immediately available or require a refresh), but the description does mention the refresh behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both parameters. The description adds value by explaining the purpose of force (override token budget warning) and the category format (key from list_tool_categories), which goes beyond the schema's basic descriptions. It doesn't add syntax details but the schema already provides those.

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 action ('Activate all tools in a category'), the resource ('category'), and the session scope. It distinguishes itself from siblings by mentioning the activation effect and the token budget guard, which is unique to this tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells the agent to use list_tool_categories to see available categories and token costs, and explains the force parameter for overriding the budget guard. It implies when to use this tool (when you need tools from a category) and provides a clear alternative for listing categories.

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

Deploy Server