`get_signals`¶

List signal definitions for this project. Signals are behaviors or patterns detected in calls (e.g. 'agent showed empathy', 'follow-up required'). Returns signal keys, descriptions, and categories. Results are narrowed to the project's verticals when those have been locked; otherwise the full catalog is returned. Use these keys to filter calls in search_calls or query_interactions.

Parameters¶

Parameter	Type	Required	Default	Description
`category`	string	no	—	Filter by signal category (e.g. 'derived', 'behavioral'). Optional.
`active_only`	boolean	no	`True`	Only return active signals. Default: true.

Example call¶

from fastmcp import Client
from fastmcp.client.auth import BearerAuth

async with Client(
    "https://mcp.chordia.ai/mcp",
    auth=BearerAuth("YOUR_APPLICATION_KEY"),
) as client:
    result = await client.call_tool(
        "get_signals",
        {
            "category": "...",
            "active_only": true
        },
    )
    print(result.content[0].text)
# Plus any of the 2 optional params from the table above.

In Claude Desktop, Cursor, or any MCP-aware client the same call is issued by the LLM automatically once the server is configured — see integrations.

Result¶

Success responses are JSON of the shape below. Optional fields are omitted when the underlying data isn't present.

{
  "signals": [
    {
      "signal_key": "empathy_acknowledged",
      "display_name": "Empathy acknowledged",
      "description": "Agent acknowledged the customer's emotional state.",
      "applicable_verticals": ["sales", "support"],
      "active": true
    }
  ],
  "count": 103
}

Auth context¶

Every call receives the connection's project_id and access_scope automatically — the caller never passes them. See Authentication & RBAC for how scope narrows results.

Errors¶

All tools return JSON. Errors are wrapped in { "error": "..." }. The most common shapes are documented in Python integration → Error shape.

get_signals¶