DevTune MCP

devtune_search_library

Read-onlyIdempotent

Hybrid-search the project Library. Current versions are returned by default.

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": {
      "query": "<query>"
    },
    "name": "devtune_search_library"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Results per page.
`query`	Yes
`cursor`	No	Opaque cursor from the previous response.
`pageSize`	No	The same setting as limit. Send either.
`includeSuperseded`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

addedInput schema / properties / limit / description
```
Added value: +"Results per page."
```

addedInput schema / properties / pageSize

Added value: +{
+  "$ref": "#/properties/limit",
+  "description": "The same setting as limit. Send either."
+}

First observedSep 9, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the useful behavioral fact that matching is hybrid (semantic plus lexical, presumably) and that current versions are the default scope, but says nothing about ranking, relevance scores, or result shape.

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?

Two short sentences with the core operation and the default-scope caveat front-loaded. Nothing is wasted, though the second sentence is doing parameter work that would be clearer if phrased as a condition.

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 five-parameter read-only search with no output schema, the description covers what the tool does and its default scope, and the schema handles pagination mechanics. It falls short only on search semantics (what 'hybrid' scores or ranks) and on how results differ from list_library.

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 coverage is only 60% – 'query' and 'includeSuperseded' carry no schema descriptions. The description's 'current versions are returned by default' implicitly maps to includeSuperseded and is genuinely useful, but it never explains query syntax, hybrid weighting, or how limit/pageSize/cursor interact beyond the schema's own notes.

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 ('Hybrid-search') and resource ('the project Library'), which tells an agent this is a query-based retrieval rather than an enumeration. It does not name or contrast with the obvious sibling devtune_list_library, so the distinction must be inferred.

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 explicit statement of when to use this tool versus devtune_list_library or devtune_read_library_item. The phrase 'returned by default' hints that superseded content is normally excluded, but the user is left to guess when that matters.

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

All DevTune MCP 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?