Skip to main content
Glama

lsp-list_domains

Lists all @ExerisDomain types known to the active LSP session, helping you discover available domain types for Exeris application work.

Instructions

List all @ExerisDomain types known to the active LSP session.

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": "lsp-list_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose one genuine behavioral fact: results come from the active LSP session rather than static build configuration. It does not say what happens when no session is active, whether the call fails, or how results are ordered or paginated.

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?

A single sentence with no filler, and the scope qualifier ('active LSP session') is placed where it is immediately useful. Nothing needs to be trimmed.

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?

For a zero-parameter list tool with no output schema and no annotations, the definition is workable but thin: it never mentions the session prerequisite explicitly as a precondition, nor how the result differs from the build-side sibling listing. The essentials for invoking it are present, but not for choosing it confidently.

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?

The tool takes zero parameters, so there is nothing for the description to clarify beyond the schema; the 4 baseline for a no-parameter tool would nominally apply. The description adds no output-shaping context, keeping it at an adequate but unremarkable level.

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?

The description names a specific verb and resource ('List all @ExerisDomain types') and scopes it to 'the active LSP session', which is more precise than a bare 'list domains'. It does not explicitly contrast itself with the similarly named sibling 'build-list_domains', so the agent must infer the distinction from the word 'LSP' alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to use this tool versus 'build-list_domains' or 'lsp-describe_domain', and no prerequisite or exclusion conditions. The phrase 'known to the active LSP session' hints at a runtime-state context, but the agent is left to infer which listing tool applies.

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