Skip to main content
Glama

Get ClawCall call settings

get_call_settings
Read-only

Read the signed-in user's voice and legacy/inbound personality, reserved-number state, and inbound-assistant availability, greeting, instructions, and knowledge base. Explains unavailable capabilities through entitlement and number status, with an informational account-access link.

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_call_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
inboundYes
outboundYes
warm_greetingYes
reserved_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: unavailable capabilities are explained via entitlement and number status, and there is an informational account-access link — useful for interpreting partial/degraded results. The remaining field enumeration is largely redundant with the existing output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with no filler, and the read action is front-loaded. The one drawback is that it is a dense comma-chain of noun phrases, which reads more like a field inventory than a structured explanation.

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 zero-parameter, read-only tool with annotations and an output schema, the description covers what is read and how unavailable capabilities surface. It stops short only of stating when to prefer this over update_call_settings or what to do if the user lacks entitlements.

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 tool takes zero parameters, so there are no parameter semantics to explain beyond what the empty schema already shows; baseline 4 applies. The description correctly adds no spurious parameter guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Read the signed-in user's voice and legacy/inbound personality, reserved-number state, and inbound-assistant availability...') and enumerates the settings categories returned. It is clearly a settings-read counterpart to update_call_settings, though it never names a sibling to sharpen the distinction.

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?

Usage is only implied by the 'Read ... settings' framing; there is no explicit statement of when to call this versus update_call_settings, no stated prerequisites (e.g., signed-in user requirement beyond 'signed-in user's'), and no exclusions. An agent can infer the read case, but nothing routes it deliberately.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.