Skip to main content
Glama

IKANGAI Vibe Support

Search Vibe Support

search
Read-only

Find notices, showcase entries and Toolbox tools by a few words, for example 'stripe refund', 'delete user data', 'supabase access rules' or 'multiplayer game'. Use this first when you know what the person is about to do. Returns the best matches with their ids; call get_notice for one in full.

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
queryYesA few plain words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and closed-corpus scope are covered structurally. The description adds genuine context beyond that: results are relevance-ranked ("best matches"), they carry ids, and full content requires a second call to get_notice — which sets the right two-step expectation. It does not discuss empty-result behavior or match limits, keeping it just shy of a 5.

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?

Two sentences, no filler, with the core capability and the 'use this first' trigger front-loaded before the follow-up tool hint. Every clause carries actionable information for selection or invocation.

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?

For a one-parameter, read-only search with no output schema, the definition covers what is searched, how to phrase the query, what comes back (ids plus ranked matches), and what to call next. Nothing an agent needs in order to select and invoke it correctly is missing.

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?

With a single parameter at 100% schema coverage, the baseline is 3; the description earns above that by supplying four concrete example queries ('stripe refund', 'delete user data', 'supabase access rules', 'multiplayer game') that demonstrate the expected keyword style rather than natural-language questions. This meaningfully constrains how an agent should phrase the query beyond the schema's terse 'A few plain words.'

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 opens with a specific verb ("Find") plus the exact resources searched (notices, showcase entries, Toolbox tools) and the matching mechanism ("by a few words"). That phrasing distinguishes it from the enumeration siblings list_notices/list_showcase/list_toolbox without the agent needing to open any schema.

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?

"Use this first when you know what the person is about to do" gives explicit ordering guidance, and "call get_notice for one in full" names the correct follow-up sibling for retrieving a single result. It stops short of an explicit when-not clause (e.g. 'browse all with list_* instead'), leaving the browse-vs-search split to be inferred from sibling names.

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.

Resources