Skip to main content
Glama

get_configuration

Get current Signal account settings for read receipts, typing indicators, and link previews.

Instructions

Get current Signal account configuration (read receipts, typing indicators, link previews)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool definition (schema) for 'get_configuration' — describes the tool with no required input parameters
    Tool(
        name="get_configuration",
        description="Get current Signal account configuration (read receipts, typing indicators, link previews)",
        inputSchema={"type": "object", "properties": {}},
    ),
  • Handler for 'get_configuration' — calls client.get_configuration() and returns the result
    elif name == "get_configuration":
        return _ok(await client.get_configuration())
  • SignalClient.get_configuration() — calls signal-cli JSON-RPC 'getConfiguration' method and returns the result dict
    async def get_configuration(self) -> dict:
        """Return current Signal account configuration flags."""
        result = await self._rpc("getConfiguration")
        return result if isinstance(result, dict) else {}
  • SignalClient.update_configuration() — related helper that toggles config flags (read_receipts, typing_indicators, link_previews, etc.)
    async def update_configuration(
        self,
        read_receipts: bool | None = None,
        typing_indicators: bool | None = None,
        link_previews: bool | None = None,
        unidentified_delivery_indicators: bool | None = None,
    ) -> None:
        """Toggle account-level configuration flags."""
        params: dict = {}
        if read_receipts is not None:
            params["readReceipts"] = read_receipts
        if typing_indicators is not None:
            params["typingIndicators"] = typing_indicators
        if link_previews is not None:
            params["linkPreviews"] = link_previews
        if unidentified_delivery_indicators is not None:
            params["unidentifiedDeliveryIndicators"] = unidentified_delivery_indicators
        if params:
            await self._rpc("updateConfiguration", params)
Behavior3/5

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

No annotations are provided, so the description carries full burden. It only states the operation without disclosing any behavioral traits such as authentication needs, rate limits, or side effects. Adequate but minimal.

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?

A single sentence that is front-loaded with the tool's purpose. No wasted words; every part earns its place.

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 zero parameters and no output schema, the description is nearly complete. It could mention the return format or structure, but the core purpose is covered. Slight gap in explaining what the configuration object contains.

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?

The input schema has zero parameters, and the description correctly adds no parameter information because none exist. Baseline for zero parameters is 4.

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 'Get' and resource 'current Signal account configuration' with concrete examples (read receipts, typing indicators, link previews). It clearly distinguishes from sibling 'update_configuration' by being a read operation.

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

Usage Guidelines3/5

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

The description implies usage for retrieving configuration, but lacks explicit guidance on when to use versus alternatives like 'update_configuration'. No exclusions or prerequisites are mentioned.

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/googlarz/signal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server