Skip to main content
Glama

Mdexa

Search dataset content (not open yet)

search_content
Read-onlyIdempotent

Planned passage search in dataset text. NOT AVAILABLE yet: returns an explanation. Use search_datasets.

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": {
      "q": "<q>"
    },
    "name": "search_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes
hintsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses the crucial operational fact that a call returns an explanation rather than results. That is the single most important behavioral trait here and it is stated plainly; it does not discuss eventual parameters or invocation mechanics, which is acceptable for a disabled stub.

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, zero filler, with the unavailability front-loaded before the redirect. Nothing could be removed without losing a distinct piece of information.

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 disabled stub with an output schema, this covers what an agent actually needs: it exists, it is not usable, and where to go instead. Only the undefined parameter meanings are left unaddressed, which matters little while the tool returns nothing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions 'q' or the 'hints' enum (on/off). With two undocumented parameters, the description does not compensate for the schema gap at all, though the tool being unavailable softens the practical impact.

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 and resource ('passage search in dataset text') and identifies the domain precisely. The title's 'not open yet' and the description's 'Planned' make clear this is a future capability, so an agent cannot mistake it for a live search.

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?

Explicitly says the tool is NOT AVAILABLE and names the alternative ('Use search_datasets'), which is the exact routing decision an agent needs. There is no ambiguity about when to reach for this versus the sibling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.