search-endpointsPerforms a deep search through paths, operations, and parameters to discover relevant API endpoints. Use this tool to find specific API capabilities, required parameters, or data models based on search keywords. Results can be passed directly into 'get-endpoint'.
| Name | Required | Description | Default |
|---|---|---|---|
| pattern | Yes | Search pattern (case-insensitive) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, and the description adds useful scope context (searches through paths, operations, and parameters) and the behavioral trait that results are compatible with get-endpoint. This goes beyond the annotations without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences that front-load the purpose and then provide usage guidance. No fluff, every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple single-parameter search tool with readOnlyHint and a clear handoff to get-endpoint, the description is adequately complete. It does not specify the return format, but the mention of passing results to get-endpoint implies a structure, and no output schema is expected for such a discovery tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single parameter 'pattern', and the description's mention of 'search keywords' aligns with but does not elaborate beyond the schema. The schema already documents case-insensitivity, so no additional semantic value is provided here.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description uses a specific verb ('Performs a deep search') and identifies the resource ('API endpoints') and scope ('paths, operations, and parameters'). It clearly differentiates from sibling tools like list-endpoints (which likely enumerates) and get-endpoint (which retrieves a single endpoint).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
States when to use the tool ('to find specific API capabilities, required parameters, or data models based on search keywords') and provides a natural follow-up action ('Results can be passed directly into get-endpoint'). It lacks explicit exclusions or alternatives, but the use case is clear enough for an agent to distinguish from sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct role: list-endpoints enumerates all paths, search-endpoints finds specific ones, get-endpoint retrieves details, execute-request makes actual API calls, and pay-with-x402 handles payment. There is no real overlap between these actions.
Most tool names follow a consistent lowercase verb-first hyphenated pattern (execute-, get-, list-, search-). pay-with-x402 is a minor deviation with a phrasal verb, but it still maintains the overall verb-led style.
Five tools is an appropriate count for a focused API client server. Each tool serves a distinct purpose in the discovery-to-execution workflow, earning its place without excess or deficiency.
The tool set covers the complete workflow: discovering endpoints, getting endpoint details, managing access via payment, and executing requests. This allows agents to fully explore and call any Vybe API endpoint with no obvious dead ends.