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

get_profile

Retrieve the authenticated user's profile information, including email, credits, and account details.

Instructions

Get the authenticated user's profile information including email, credits, and account details

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It mentions 'authenticated user', implying authentication is required, but does not detail side effects, rate limits, or error conditions. For a simple read, this is adequate but not thorough.

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 a single sentence with action, resource, and examples. It is front-loaded and contains no fluff, earning high marks for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description lists some fields but is not exhaustive. It provides a general idea of return data but lacks detail on structure or mandatory fields. Acceptable for simple tool but not fully comprehensive.

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

Parameters4/5

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

There are no parameters, so schema coverage is 100%. The description adds no param info, which is acceptable as baseline for zero parameters.

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 action 'Get' and the specific resource 'authenticated user's profile information', and lists example fields (email, credits, account details). It distinguishes itself from sibling tools which handle 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 Guidelines3/5

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

The description implies usage for retrieving profile data of the authenticated user, but does not provide explicit guidance on when to use or not use it, nor contrasts it with alternatives. While siblings are different, no usage context is given.

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