Skip to main content
Glama
KaiCalls MCP Server

KaiCalls MCP Server

Official

Set What Clients See About You

agency_clients_set_client_profile
Idempotent

Sets the support contact and relationship note clients see in their dashboard, so agencies can define who to contact and how they work together. Requires an owner or admin; sends no messages.

Instructions

Sets who your clients should contact about their line and one or two sentences on how you work with them. Shown in every client's dashboard. Requires an agency owner or admin. Sends nothing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "partnerId": "<partnerId>"
    },
    "name": "agency_clients_set_client_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
partnerIdYesThe agency (partner) workspace ID.
clientSupportContactNoEmail or phone your clients should use; null clears it.
clientRelationshipNoteNoHow you work with your clients, up to 600 characters; null clears it.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when success is false
receiptNo
successYesWhether the tool completed successfully

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description adds two things the structured data lacks: an authorization requirement (owner/admin) and the assurance 'Sends nothing', which tells the agent no notifications go out — a meaningful distinction from the alerts siblings. It does not describe what happens to existing values or how other admins' settings interact, so it falls short of a 5.

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?

Three short sentences, front-loaded with purpose, followed by visibility, prerequisite, and side-effect. No filler or redundant restatement of the title.

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 three-parameter mutation with an output schema and full annotations, the description covers purpose, permissions, and notification behavior. The only gap is the lack of explicit routing versus the client-alerts tools, which is a minor omission given the output schema handles return values.

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 description coverage is 100%, so every parameter already carries its own meaning including the null-clears behavior. The description adds only loose framing ('who your clients should contact', 'one or two sentences'), which mildly clarifies intent but doesn't extend beyond what the schema states.

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 names a specific verb and resource — setting the support contact clients see and a short note about how the agency works — and the title reinforces it. It is clear what is being configured, though it never contrasts itself with the adjacent agency_clients_set_client_alerts sibling, which an agent must distinguish by inference.

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

Usage Guidelines4/5

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

It gives real usage context: the value is 'Shown in every client's dashboard' and the caller must be an agency owner or admin. There is no explicit when-not guidance or named alternative for alert configuration, but the audience and prerequisite make the invocation context unambiguous.

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

Deploy Server

Other Tools