Skip to main content
Glama
Leximo-AI

leximo-ai-call-assistant-mcp-server

Official
by Leximo-AI

create_assignment

Create a phone call assignment after gathering details, selecting an agent, and confirming with the user. Specify agent, number, time, language, and task.

Instructions

Create a new phone call assignment. Do NOT call this tool immediately. Follow this workflow:

  1. Gather info: Ask the user for any missing details — phone number, desired call time, timezone, and language. Do NOT guess or fabricate values.

  2. Select agent: Call list_agents to show available agents. Recommend one based on the task or let the user choose.

  3. Improve task: Call get_assignment_proposals with the user's task description, then present the enhanced version for the user to approve or edit.

  4. Confirm: Summarize all parameters (agent, name, datetime, timezone, phone number, language, task) and get user confirmation before calling this tool. Only call create_assignment after completing all steps above.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentIdYesID of the AI agent to use. Call list_agents first to see available agents.
nameYesName for this assignment (e.g. the business or person being called)
datetimeYesWhen to make the call, in ISO 8601 format (e.g. 2025-06-15T14:30:00)
timezoneYesTimezone for the datetime (e.g. America/New_York, Europe/London)
phoneNumberYesPhone number to call in international format (e.g. +1234567890)
languageCodeYesLanguage code for the call (e.g. en, es, fr, de)
taskYesDescription of what the AI agent should do during the call (e.g. 'Book a table for 2 at 7pm on Friday')
Behavior3/5

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

No annotations exist, so the description carries full burden. It discloses the creation action but does not discuss side effects (e.g., whether scheduling is immediate, if it sends notifications, or requires special permissions). The workflow hints at safety (user confirmation) but lacks explicit behavioral traits beyond 'create'.

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 front-loaded with the core purpose and immediate prohibition. The workflow is detailed but each sentence is necessary for safe operation. Slightly longer than ideal but earns its length through clarity and procedural value.

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?

The description fully covers the tool's preconditions, required parameters, and user confirmation step. Despite no output schema, it provides enough context for an agent to use the tool correctly within the defined workflow. No gaps identified.

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 each parameter has a clear schema description. The description adds workflow context (e.g., 'do not guess values') but does not provide semantic detail beyond the schema. Baseline score of 3 is appropriate.

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 explicitly states 'Create a new phone call assignment' with a specific verb and resource. It clearly distinguishes from sibling tools like list_agents, get_assignment_proposals, and delete_assignment by embedding the tool in a multi-step workflow.

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?

The description provides a complete step-by-step workflow: gather info, select agent via list_agents, improve task via get_assignment_proposals, confirm with user, and only then call this tool. It explicitly warns 'Do NOT call this tool immediately' and identifies prerequisites.

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/Leximo-AI/leximo-ai-call-assistant-mcp-server'

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