KaiCalls

Get Scam Call Screening

get_scam_screening

Read-onlyIdempotent

Read how the business screens scam calls: the mode (off; label, the default, which answers every call and marks likely scams in the call log; or screen, which sends callers with a strong scam sign to a take-a-message screen), the numbers that are never screened, and the most recent calls caught as scams.

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

Input Schema

Name	Required	Description	Default
`business_id`	No	Business ID (optional only when the token has exactly one accessible business)

Output Schema

Name	Required	Description
`error`	No	Present when success is false
`success`	Yes	Whether the tool completed successfully
`settings`	No
`is_default`	No
`business_id`	No
`recent_flagged_calls`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish this is a safe, idempotent read. The description adds useful behavioral context by explaining the default 'label' mode, the 'screen' behavior, and that unscreened numbers and recent scam catches are included. It does not cover limits on 'most recent calls', but that is a minor omission.

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?

The description is a single dense sentence with the resource front-loaded, and every clause contributes useful information. The long parenthetical explaining modes is somewhat heavy but remains clear and purposeful.

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?

This is a simple read tool with one optional parameter and an output schema. The description covers the core returned content and mode semantics, so an agent has enough information to select and invoke it correctly.

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

Parameters3/5

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

There is one optional parameter and the schema fully documents it, including the single-accessible-business condition. The description adds no parameter-specific meaning, so the baseline of 3 is appropriate when schema coverage is high.

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 states a specific verb and resource: reading how a business screens scam calls. It names the exact data returned: screening mode, unscreened numbers, and recent calls caught as scams, which clearly distinguishes it from generic settings or call-list siblings.

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 tool's purpose; there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. An agent can infer this is for inspecting scam screening configuration, but nothing routes it against related tools like get_operational_settings.

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

All KaiCalls tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.