Skip to main content
Glama
Sign In

Dedox

by ai.dedox
OverviewDiscussionsAdmin

Search articles

search_articles
Read-only

Search articles using full-text search

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (1-100, default: 50)
queryYesSearch query
offsetNoNumber of results to skip (default: 0)
knowledgeBaseIdNoFilter by knowledge base ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

The description adds very little behavioral context, relying almost entirely on the provided annotations (readOnlyHint: true). It doesn't describe how the search is scoped beyond the phrase 'full-text search' or any potential performance implications.

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?

The definition is extremely concise and front-loads the core functionality in a single, clear sentence with no unnecessary filler.

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?

Given the high schema coverage and safety hints in the annotations, the definition is adequate but fragile. The lack of usage guidelines makes it incomplete for an agent trying to decide between this and related list tools.

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%, establishing a baseline of 3. The description reinforces the purpose of the `query` parameter by specifying 'full-text search' but adds no semantic meaning to the other filtering parameters like `knowledgeBaseId`.

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?

The description clearly states the action (Search) and the resource (articles), and the qualifier 'full-text search' helps distinguish it from potential generic listing functions like `list_articles`. However, it lacks differentiation from other specific search tools if they exist.

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

Usage Guidelines1/5

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

The description offers no guidance on when to use this tool versus alternatives like `list_articles`. It provides no context on the expected volume of results or the quality of the search engine.

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

All Dedox toolsInspect
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