Skip to main content
Glama

Media Generator — Images, Videos & Audios

search

Search for tools and resources available in the Saifs AI MCP server.

This tool allows ChatGPT to discover available tools and their capabilities. It searches through tool descriptions, names, and functionality to find relevant tools.

Args: query: The search query to find relevant tools

Returns: A JSON string containing search results with tool information

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the search index scope (tool descriptions, names, functionality), which is genuinely useful. However it says nothing about whether the operation is read-only/safe, any auth or rate constraints, or result limits, which is a notable gap for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, which is good, but the second sentence ('allows ChatGPT to discover available tools and their capabilities') largely restates the first, and the 'Returns' section is redundant given an output schema exists. Roughly a third of the text does not earn its place.

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 discovery tool with an output schema (so return values need not be described), the description covers purpose and what the search operates over. What an agent needs to call it correctly is present; only behavioral caveats (safety, limits) are absent, which is minor at this complexity.

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 0% and the single 'query' property has no schema-level documentation, so the description's 'The search query to find relevant tools' is the only source of semantics. It conveys the parameter's intent but adds nothing about matching behavior, expected syntax, or query construction.

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 (search) and resource (tools and resources in the Saifs AI MCP server), and explicitly frames it as a discovery tool for capabilities. This unambiguously separates it from all 17 siblings, which are concrete media/token/health operations, none of which is a discovery tool.

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?

Usage is implied rather than stated: 'allows ChatGPT to discover available tools' suggests when to reach for it, but there is no explicit when-to-use trigger, no when-not guidance, and no mention of an alternative path. Adequate but with clear gaps.

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.