Skip to main content
Glama

Discover Tools

discover_tools
Read-onlyIdempotent

Search available tools by keyword across 17 Apple ecosystem modules.

Instructions

Search available tools by keyword.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query — e.g. 'calendar', 'send email', 'music playback'
limitNoMax results (default 20)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
matchesYes
totalNo
methodNo
hintNo
Behavior3/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds no further behavioral context beyond what annotations convey, which is adequate though not enhanced.

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?

The description is a single, concise sentence that is front-loaded with the core action. Every word earns its place with no extraneous content.

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?

Given the simple nature of the tool, the presence of an output schema, and comprehensive annotations, the description is complete. It clearly defines the tool's purpose without needing to explain return values or additional behavior.

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 coverage is 100%, with well-described parameters (query, limit). The description 'Search available tools by keyword' is consistent but does not add significant meaning beyond the schema's parameter descriptions.

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 'Search available tools by keyword' is specific and clearly indicates the tool's function. It distinguishes itself from sibling tools like search_notes or search_events by focusing on discovering tools rather than content.

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?

While no explicit when/when-not or alternatives are given, the purpose is self-evident. The description clearly implies it's for searching tool names/descriptions, which is distinct from other search tools on the server.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/heznpc/AirMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server