Skip to main content
Glama
Sign In
leximo-ai-call-assistant-mcp-server

leximo-ai-call-assistant-mcp-server

Official
by Leximo-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_notifications

Retrieve a paginated list of notifications for the current user, including call completion events and system notifications. Use limit and offset parameters to control the number and starting point of results.

Instructions

Get paginated list of notifications for the current user. Includes call completion events and system notifications.

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": "list_notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of notifications to return (default: 20, max: 100)
offsetNoNumber of notifications to skip (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It mentions 'paginated list' and the types of notifications, but does not disclose behavioral traits like authentication requirements, ordering, filtering capabilities, or rate limits. The description is moderately helpful but lacks depth.

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?

The description is two sentences with no wasted words. It front-loads the purpose and includes relevant details about content type.

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?

Given the tool's simplicity (2 parameters, no output schema, no nested objects), the description covers the essentials. Lacks return structure details, but the expected output is implied. For a list tool, this is sufficient.

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% with clear parameter descriptions (limit with default and max, offset with default). The description adds no additional meaning beyond the schema, so baseline 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 clearly states the verb 'Get', the resource 'paginated list of notifications', and the scope 'for the current user'. It also specifies the types of notifications included (call completion events and system notifications), which distinguishes it from sibling tools that deal with assignments, agents, etc.

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?

While the description does not explicitly state when to use this tool vs alternatives, the context of sibling tools shows no other tool listing notifications, so the purpose is clear. A minor improvement would be an explicit 'Use this to...' statement, but it's adequate.

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