Skip to main content
Glama

resource_search

Read-onlyIdempotent

Search existing potentials and native examples by keyword or Chinese/English alias, and check catalog_total to distinguish no matches from an empty catalog.

Instructions

Search existing potentials and native examples using keywords and Chinese/English aliases. catalog_total distinguishes no matches from an empty catalog; retry fewer terms or query='' to inspect it. indexed is metadata; resource_get rechecks files. Read examples with resource_file_read and follow next_offset while more=true.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
queryNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

While annotations cover safety, the description provides crucial behavioral context regarding execution flow and result interpretation. It instructs the agent on how to navigate the results ('follow next_offset while more=true'), which is vital for a pagination tool.

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?

The description is dense, but every phrase serves an operational or differentiation purpose. It prioritizes high-value functional guidance and comparative context over boilerplate descriptions.

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 complexity of multilingual searching, pagination, and the lack of robust input schema coverage, the description is remarkably complete. It preemptively answers several common agent questions about result handling and tool interaction.

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?

Since schema coverage is 0%, the description adds vital semantic meaning to the search parameters. It explains that 'indexed is metadata' and clarifies the difference between searching here and calling 'resource_get' to recheck files.

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?

The description clearly identifies the action (Search) and the resource (existing potentials and native examples). It specifies that the search uses keywords and Chinese/English aliases, which is a clear functional definition.

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?

This is excellent, highly specific guidance. It explains how to handle result ambiguity ('catalog_total distinguishes no matches from an empty catalog') and provides explicit operational tips ('retry fewer terms or query='' to inspect it').

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