Skip to main content
Glama
Sign In
Lenx MCP Server

Lenx MCP Server

by ThinkCol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

lenx_list_tasks

Retrieve a paginated list of monitoring tasks for the authenticated user. Use page and size parameters to navigate through tasks.

Instructions

List monitoring tasks accessible to the authenticated user, with pagination support.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
sizeNoItems per page (default: 10, max: 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A3.7/5.0
Behavior3/5

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

Description mentions authentication context ('accessible to the authenticated user') and pagination, but lacks details on ordering, filtering, or rate limits. With no annotations, more behavioral disclosure would be beneficial.

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?

Single sentence, front-loaded with key information (verb and resource), no extraneous words.

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?

No output schema exists, but description does not specify what fields or format the list returns. Users may need to infer from context; could benefit from stating return structure.

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 provides full descriptions for both parameters (page, size). Description only mentions 'pagination support' without adding new semantic details beyond schema.

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?

Description clearly states verb 'List' and resource 'monitoring tasks', distinguishing from sibling tools like lenx_get_task (single task) or lenx_create_task.

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?

No explicit guidance on when to use this tool vs alternatives like lenx_get_task for a single task, nor any when-not conditions.

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