Skip to main content
Glama

Search Dalux Capabilities

dalux_search_capabilities
Read-onlyIdempotent

Search Dalux MCP server capabilities and examples to decide which Dalux tool to call first.

Instructions

Search the Dalux MCP server capabilities and examples. Use this first when deciding which Dalux tool to call.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / query / maxLength
      Added value: +200
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered without the description. The description adds workflow positioning but says nothing about what the search actually returns, how queries are matched (keyword, substring, semantic), or what an empty query yields.

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 with zero filler, and the action is front-loaded ahead of the workflow guidance. Nothing redundant with the name or title.

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 simple read-only search tool with no output schema, the description is close to adequate, but it leaves the agent guessing about result shape (capability list vs. examples vs. tool names) and about the effect of an omitted or empty query. Those gaps matter for a tool whose whole job is discovery.

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?

With 2 parameters and 0% schema description coverage, the description carries the full burden, yet it never mentions "query" or "limit". The names are self-explanatory enough that an agent can guess, but no added meaning (matching rules, empty-string behavior, result-count cap) is provided.

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?

States a specific verb ("Search") and a specific resource ("Dalux MCP server capabilities and examples"), which is clearly distinct from every sibling tool that acts on Dalux data. An agent can tell this is the discovery/router tool without opening any schema.

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

Usage Guidelines4/5

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

"Use this first when deciding which Dalux tool to call" gives explicit, actionable sequencing guidance relative to all siblings. It stops short of stating when not to use it (e.g., once the target tool is already known) or what happens on repeated/empty queries, but the core routing context is clear.

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