mcp-server-check

Official

by check-technologies

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Search Tools

search_tools

Read-onlyIdempotent

Search available API tools by keyword. Returns matching tools with full parameter schemas. Supports synonym matching and toolset filtering.

Instructions

Search for available API tools by keyword.

Returns matching tools with their full parameter schemas, ready for use with run_tool. Call with an empty query to see all available toolsets. Supports synonym matching (e.g. "pay employees" finds payroll tools).

query: Search keywords (e.g. "list companies", "create employee", "payroll"). toolset: Optional toolset name to restrict search (e.g. "companies", "employees"). limit: Maximum number of results (default 20).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`toolset`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 8, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds synonym matching and behavior with empty query, enhancing understanding.

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?

Description is concise, well-structured with purpose first then parameters, no redundant sentences.

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?

Covers all aspects: purpose, usage, parameters, and exit criteria. Given output schema exists, return values are not needed.

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

Parameters5/5

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

Schema coverage is 0%, but description fully explains all three parameters with examples and defaults, compensating completely.

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 available API tools by keyword', uses specific verb and resource, and distinguishes from siblings by noting results are ready for use with run_tool.

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

Usage Guidelines4/5

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

Provides guidance on empty query for all toolsets and optional toolset restriction, plus synonym matching. Lacks explicit when-not-to-use but is clear overall.

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

Deploy Server