glimind

find_tool

Read-only

WHEN TO CALL: before call_remote_tool, to find the tool for a task and get only its input schema. Pass query (what you want to do) for the best matches, the first with its schema; server (id or short name) to list that server's tools; server + tool for one tool's schema. Each result says whether it can be called through the gateway.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_tool"
  }
}

Input Schema

Name	Required	Description
`tool`	No	With server: the tool whose input schema you want.
`limit`	No	Max results for a query (default 5, max 10).
`query`	No	What you want to do, in plain language (e.g. 'search the web').
`apiKey`	No	Optional Glimind key (from create_key) if your MCP connection has none.
`server`	No	A server id or short name (e.g. 'exa').

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

addedInput schema / properties / apiKey

Added value: +{
+  "description": "Optional Glimind key (from create_key) if your MCP connection has none.",
+  "type": "string"
+}

AddedNov 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Adds context beyond annotations: only the input schema is returned (not the tool itself), the first query match comes with its schema, defaults and the max of 10 for limit, and per-result callability through the gateway. Missing details on failure modes or what an uncallable result means, but annotations already cover the read-only/no-open-world profile.

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

Conciseness4/5

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

Front-loads the trigger condition and packs three modes into compact clauses; dense but well ordered. Slight cost in readability from the semicolon-chained mode list, though nothing is wasted.

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 an agent-facing discovery tool with full schema coverage and no output schema, the description covers how to query, expected return granularity, and follow-up behavior. It leaves the shape of results (fields per match) implicit, which is the main remaining gap.

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

Parameters2/5

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

Schema coverage is 100%, so the baseline would be 3, but the description restates the same server/tool/query semantics already in the schema without adding new meaning. The one piece of added information, the limit default of 5 and max of 10, is also already in the schema description, so the description contributes nothing beyond structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states a specific verb (find) and resource (tool) and explains the three invocation modes: query for ranked matches, server to list a server's tools, server+tool for one schema. It distinguishes itself from siblings like call_remote_tool indirectly via the routing sentence, though it never names other discovery siblings such as discover_tools or select_tools.

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

Usage Guidelines5/5

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

Opens with an explicit 'WHEN TO CALL: before call_remote_tool', establishing ordering relative to the invocation tool, then explains each mode's selection condition. It also notes results indicate gateway callability, which guides the follow-up decision.

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

All glimind tools Inspect

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

Need Help?