ContextStream MCP Server

Tool search

tool_search

Read-onlyIdempotent

Search available tools and hidden operations, then call them directly or queue for deferred execution.

Instructions

Search available tools and hidden operations, then call direct tools or use execute_operation for deferred capabilities.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tool_search"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.74May 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already provide safety hints (readOnly=true, idempotent=true). The description adds value by revealing it can find hidden operations and that execute_operation is for deferred capabilities, adding behavioral context beyond annotations.

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?

The description is a single, well-structured sentence that is front-loaded with the primary action and includes follow-up guidance. No wasted words; every phrase adds value.

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?

While the description covers the basic purpose and post-search actions, it lacks specificity about how the search works (e.g., criteria, results format). With no output schema, more detail on what the search returns would improve completeness.

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

Parameters4/5

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

No parameters are defined in the input schema, so schema description coverage is trivially 100%. The description does not need to explain parameters; baseline for 0 params is 4, and no additional info is required.

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?

Description clearly states the tool searches for tools and hidden operations, with a specific verb ('Search') and resource ('available tools and hidden operations'). It also outlines follow-up actions, distinguishing it from sibling tools like 'search' or 'execute_operation'.

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

Usage Guidelines3/5

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

The description implies usage by mentioning 'then call direct tools or use execute_operation', but it does not explicitly state when to choose this tool over alternatives like the generic 'search' or 'execute_operation' tools. Guidance on context is minimal.

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