symfony-agent-mcp

get_active_tools

Identify active tool categories, exposed tool count, and estimated token cost to manage your current context budget.

Instructions

Show which tool categories are currently active in this session, how many tools are exposed, and the estimated token cost. Use this to understand your current context budget.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_active_tools"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 22, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations exist, so behavioral disclosure falls entirely on the description. The word 'Show' communicates read-only introspection, and the description explicitly reveals that the tool returns session state, a count of exposed tools, and an estimated token cost. It does not explicitly say it has no side effects, but the verb and zero-parameter design make that clear enough.

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 first sentence front-loads exactly what the tool reports, and the second sentence explains why the agent would call it. Every word earns its place.

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 zero-parameter, no-output-schema tool, this description is fully adequate. It conveys the tool's scope, output, and a motivating use case. Nothing essential is missing for a model to invoke the tool appropriately.

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?

With zero parameters and 100% schema coverage, the schema is already complete and the description has no parameter details to add. The description does contribute some useful semantics by clarifying what the response will contain, namely active categories, count of exposed tools, and token cost.

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 uses a specific verb, 'Show', and names a clear resource: the tool categories that are currently active in this session, plus a count and estimated token cost. The phrase 'currently active' and the context-budget emphasis clearly set it apart from sibling tools like list_tool_categories or search_tools.

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 directly tells the agent when to use the tool: 'Use this to understand your current context budget.' It clearly establishes a use case, though it does not explicitly mention exclusions alternatives such as when the agent should use list_tool_categories instead.

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

Deploy Server