Skip to main content
Glama

Solana MCP by Vybe

by io.github.vybenetwork
OverviewDiscussionsAdmin

Search API Endpoints

search-endpoints
Read-onlyIdempotent

Performs 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'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patternYesSearch pattern (case-insensitive)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
matchesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "matches": {
+      "items": {
+        "properties": {
+          "method": {
+            "type": "string"
+          },
+          "path": {
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds behavioral context about the deep search scope and the integration with get-endpoint, which goes beyond the annotations. There is no contradiction.

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?

Three sentences, each earning its place: purpose, usage, and workflow integration. No unnecessary words. Front-loaded with the action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read-only search tool with an output schema, the description covers purpose, usage, and workflow. It doesn't discuss result limits or output details, but the output schema is expected to handle that. The description is sufficient for an agent 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?

The schema covers the only parameter 'pattern' with a description 'Search pattern (case-insensitive)'. The description doesn't add much beyond that, only referring to 'search keywords'. Since schema coverage is 100%, a baseline of 3 is appropriate; the description adds minimal value but doesn't need to compensate.

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?

The description clearly states the verb 'search' and the resource 'API endpoints', and specifies the search scope (paths, operations, parameters). It also distinguishes from siblings by emphasizing 'deep search' and the workflow integration with 'get-endpoint', making it clear when to use this tool over list-endpoints or others.

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?

It explicitly says 'Use this tool to find specific API capabilities, required parameters, or data models based on search keywords.' This gives clear usage context. It also notes that results can be passed to 'get-endpoint', implying a follow-up workflow. However, it doesn't explicitly contrast with alternatives like 'list-endpoints', so a score of 4 is appropriate.

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

All Solana MCP by Vybe 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