KaiCalls

Get Trust Level

get_trust_level

Read-onlyIdempotent

Read one business's KaiCalls trust level (Sprout, Verified, Trusted, Pro, Partner): the current level, the steps to the next one with progress, what each level unlocks, today's outbound calls and texts against current effective account limits, and any hold. Badge progress does not itself establish higher call or text caps. focus 'ladder' explains every level; focus 'level' with level explains one. Read-only: returns saved standing or computes missing/stale standing without saving it or sending notifications. recheck_trust_level recomputes and saves current standing. Levels are earned, never set: no tool can raise one.

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

Input Schema

Name	Required	Description
`focus`	No	'standing' (default): the current level and next steps. 'ladder': every level. 'level': the one named in level. 'outbound': today's outbound calls and texts against the limits this level allows, and the step that raises them.
`level`	No	A level key or name, e.g. 'pro'. Used with focus 'level'.
`business_id`	No	Business ID (optional only when the token reaches exactly one business).

Output Schema

Name	Required	Description
`held`	No
`line`	No
`next`	No
`error`	No	Present when success is false
`level`	No
`moved`	No
`detail`	No
`ladder`	No
`meters`	No
`quests`	No
`success`	Yes	Whether the tool completed successfully
`progress`	No
`rechecked`	No
`business_id`	No
`computed_at`	No
`previous_level`	No
`next_opens_later`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

removedInput schema / properties / recheck

Removed value: -{
-  "description": "Recompute from live activity now, e.g. right after a card was added.",
-  "type": "boolean"
-}

AddedOct 14, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description's read-only claims largely restate that. It does add genuinely new behavioral context: missing or stale standing is computed but not persisted, no notifications are sent, and badge progress does not itself raise call or text caps — a non-obvious caveat an agent would otherwise get wrong.

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 scope statement is front-loaded and every sentence carries operational content, with no filler. The first sentence is a long chain of clauses that would read better as a list, but nothing is wasted.

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?

An output schema exists, so return shape need not be explained. For a read-only, three-parameter tool with full schema coverage, the description covers scope, mode routing, persistence behavior, and the sibling relationship — nothing an agent needs is missing.

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?

Schema coverage is 100% and the enum description for focus already spells out all four modes, so most of the description's focus explanations are redundant restatement. The one real addition is the caveat that badge progress does not establish higher caps, which clarifies what the 'outbound' view does and does not imply — enough to edge above pure repetition but still baseline territory.

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?

States a specific verb and resource ('Read one business's KaiCalls trust level') and enumerates the exact value space (Sprout, Verified, Trusted, Pro, Partner) plus what is returned: current level, next steps, unlocks, outbound usage against limits, and holds. It is clearly distinguishable from recheck_trust_level, which is named as the recompute-and-save counterpart.

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

Usage Guidelines5/5

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

Gives explicit routing by focus mode ('ladder' explains every level; 'level' with level explains one) and names the alternative tool with its selecting condition: use recheck_trust_level to recompute and save, this one to read without saving. It also rules out an impossible use case up front ('Levels are earned, never set: no tool can raise one').

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.