Skip to main content
Glama

jdx_services

Lists META-INF/services SPI registrations across workspace jars, with optional filtering by service or provider class name, artifact glob, regex, and result limits.

Instructions

List META-INF/services SPI registrations across the workspace jars. Omit query to list every registration; with a query, match the service interface FQN or a provider class FQN. Does not read module-info provides (use jdx_modules for that).

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

Input Schema

NameRequiredDescriptionDefault
inNoOnly matches from artifacts whose label matches this glob.
limitNoMaximum rows shown (default 50); the rest become a truncation footer.
queryNoOptional subject: package glob (ls), artifact glob (tree), service/provider substring (services), or module/package/service substring (modules). Empty lists everything.
regexNoTreat query as a Java regex.
excludeNoSkip matches from artifacts whose label matches this glob.
workspaceNoNamed workspace to answer from (default: the workspace the server was started with). Stored workspaces only.
ignoreCaseNoCase-insensitive substring match (ignored under regex; use (?i) there).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden, and it does disclose the key boundary — it only reads META-INF/services and deliberately excludes module-info provides. The listing intent implies a safe read, and the limit/truncation behavior is covered by the schema. It stops short of describing result shape or ordering, so it is not fully self-sufficient.

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?

Three short sentences, front-loaded with the resource scope, then the calling modes, then the exclusion. No filler and no repetition of schema fields.

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?

For a seven-parameter list tool with full schema coverage and no output schema, the description supplies the essential semantics and the sibling boundary. Minor gaps remain around result shape and ordering, but nothing that would cause a misinvocation.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning the schema does not: what omission of query produces and that query matches against service or provider FQNs specifically for this tool. That disambiguates the generically worded query parameter in the shared 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?

The opening sentence names a specific verb (List), a specific resource (META-INF/services SPI registrations), and an explicit scope (workspace jars). It also carves out what it does not do and names the sibling that does it, so an agent can distinguish it from jdx_modules without opening either schema.

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

Usage Guidelines5/5

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

It states the two calling modes precisely: omit query to list everything, or supply a query matching a service interface FQN or provider class FQN. It also names the alternative (jdx_modules) for module-info provides, which is an explicit when-not-to-use rule.

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