Skip to main content
Glama
Sign In
Courtship

Courtship

by grimmdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

discover_tools

Search available tools by keyword or intent to find what you need without loading full schemas into context. Accepts a query and optional result limit.

Instructions

Search available tools by keyword or intent without loading full schemas into context.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesKeyword or action (e.g. 'physics', 'screenshot', 'joypad', 'crash')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the behavioral burden. It discloses only that full schemas are not loaded into context, but it does not state whether the search is read-only, what it returns, how results are ranked, or how limit affects output.

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 front-loaded sentence with no redundant wording. Every clause contributes either the core action or the lightweight discovery benefit.

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

Completeness3/5

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

The tool is simple, with two parameters and no output schema, so a short description can be adequate. Still, it leaves the limit behavior and the shape of returned search results unexplained, which an agent would need in order to use the tool confidently.

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?

The schema covers only 50% of parameters: query has a description with examples, while limit has no description. The tool description adds the idea of searching by 'intent' beyond keywords, but it does not explain the limit parameter or otherwise compensate for the coverage gap.

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 gives a specific verb and resource: 'Search available tools'. It also distinguishes the operation from loading full schemas into context, which implicitly separates it from sibling tools such as load_tool_schema.

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?

The phrase 'without loading full schemas into context' implies the tool is for lightweight discovery before schema loading or invocation. However, it does not explicitly say when to use this versus load_tool_schema or how search results should feed into call_tool.

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

Deploy Server

Other Tools