DevExpress Documentation

Search DevExpress Documentation

devexpress_docs_search

Read-onlyIdempotent

Search DevExpress documentation for a given technology and a question. If you want to search for multiple technologies, pass them as a list. This tool returns only snippets/excerpts; full content requires a follow-up devexpress_docs_get_content call on a chosen URL. ALWAYS call devexpress_docs_search before ANY devexpress_docs_get_content call in a user request chain.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "technologies": "<technologies>",
      "question": "<question>"
    },
    "name": "devexpress_docs_search"
  }
}

Input Schema

Name	Required	Description	Default
`question`	Yes	Your specific question, phrased in natural language. Describe what you're trying to accomplish and name the relevant controls, APIs, or features. This tool performs semantic search using a text embedding model, so the query must be semantically meaningful.
`technologies`	Yes	List of DevExpress technologies to search within. Use specific technology names like 'WindowsForms', 'XtraReports', 'OfficeFileAPI' etc. You must choose from the allowed set.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, openWorld=true, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: results are excerpts only, and a follow-up call is required for full content. It stops short of describing result counts, ranking, or pagination behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the core purpose and then the workflow constraint; no filler. Slightly verbose in restating the tool name inside the ordering rule, which is already in the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only search tool with strong annotation coverage and no output schema, the description tells the agent everything needed: what it returns (snippets), what to do next (get_content), and the mandatory call ordering. Nothing required for correct invocation is missing.

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 description coverage is 100%, so both parameters already document their meaning, including the semantic-embedding requirement for 'question' and the allowed technology set. The description's only added value is the multi-technology-as-list note, which the array/minItems schema already implies. Baseline 3 is correct.

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+resource ('Search DevExpress documentation') with the two required inputs named, and explicitly distinguishes itself from the sibling by noting it returns only snippets while full content lives in devexpress_docs_get_content. An agent can route between the two tools 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?

Gives an explicit ordering rule ('ALWAYS call devexpress_docs_search before ANY devexpress_docs_get_content call in a user request chain') and names the alternative tool, which is exactly the when/when-not/alternative guidance the dimension asks for. The multi-technology batching hint adds a second piece of actionable usage guidance.

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

All DevExpress Documentation 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?