LexGO Jobs

List LexGO events

list_events

Read-onlyIdempotent

List upcoming scheduled legal trainings and events on LexGO. On-demand webinars are excluded.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`domain`	No
`language`	No

Output Schema

Name	Required	Description	Default
`events`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026
- changedOutput schema / properties / events / items / properties / event_ends_at / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / events / items / properties / event_starts_at / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
First observedSep 15, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes the temporal filter and the exclusion of on-demand content, but says nothing about pagination behavior, default page size, or result ordering, which matters for a list tool with a cursor parameter.

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?

Two short sentences, front-loaded with the action and scope, with the exclusion immediately following. No filler or redundancy.

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?

Because an output schema exists, return values need not be described, and the annotations cover safety. However, for a four-parameter listing tool with zero parameter documentation, the absence of any pagination or filtering explanation leaves an agent unable to use limit, cursor, domain or language with confidence.

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

Parameters2/5

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

Schema description coverage is 0% for four parameters, so the description carries the full burden and delivers nothing: limit, cursor, domain (be/lu) and language (nl/fr/en) are never explained. The enum values are listed in the schema but their meaning (market/region, response language) and defaults are left entirely to guesswork.

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?

States a specific verb and resource ('List upcoming scheduled legal trainings and events on LexGO') plus a scope exclusion ('On-demand webinars are excluded'), which lets an agent distinguish a listing call from the singular sibling get_event. It stops short of naming any sibling explicitly, so differentiation is inferential rather than stated.

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 phrase 'upcoming scheduled' and the exclusion of on-demand webinars give implicit selection criteria, but there is no explicit statement of when to use this versus get_event or search_jobs. The agent must infer that this is the browse-all path and get_event is the single-item lookup.

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

All LexGO Jobs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?