Skip to main content
Glama

TridentStack Control Docs

Search TridentStack docs

search_docs
Read-only

Full-text search over TridentStack Control's customer documentation (guides, API reference, changelog, roadmap). Returns ranked results with titles, URLs, and snippets. Use this first to find relevant docs, then get_doc to read one in full. It also covers reference formats, including the Endpoint Checks import file format, so an assistant can write a check file a customer imports. Before writing or making calls to the TridentStack Control REST API, search for "API rate limits and efficient polling": it explains which endpoints answer a question in the fewest requests and how to handle a 429.

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_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 8)
queryYesNatural-language or keyword query
sourceNoRestrict to one content type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world scope, so the safety profile is covered. The description goes beyond that with the return shape ('ranked results with titles, URLs, and snippets') despite no output schema existing, and discloses unusual coverage (reference formats such as the Endpoint Checks import file) that an agent could not otherwise guess.

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?

Front-loaded with purpose and return format before usage routing, which is the right order. The final sentence is long and packs two claims (endpoint efficiency plus 429 handling), making it slightly heavier than necessary, but no sentence is filler.

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?

No output schema exists, and the description compensates by describing the ranked-result shape. For a three-parameter read-only search tool it covers purpose, return values, follow-up routing, and the pre-call discovery workflow, leaving nothing an agent needs in order to call it correctly.

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 all three parameters are already documented, and the default of 8 and the 1-25 bound live in the schema. The description only indirectly reinforces the `source` enum by enumerating the same four content types it lists in the enum; it adds nothing about query syntax or how natural-language versus keyword input behaves.

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 and resource ('Full-text search over TridentStack Control's customer documentation') and immediately scopes it to four content types: guides, API reference, changelog, roadmap. It also distinguishes itself from the sibling read tool by positioning get_doc as the follow-up step for reading a single doc in full.

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 explicit sequencing: 'Use this first to find relevant docs, then get_doc to read one in full.' It adds a concrete precondition for API work ('Before writing or making calls to the TridentStack Control REST API, search for ...'), naming both the query to run and why it matters (fewest requests, handling 429).

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.

Resources