Skip to main content
Glama

Metis — Search Notes

search_notes

Search markdown notes across domains, projects, and library using case-insensitive substring search with surrounding context lines. Specify scope, limit results, and truncate context.

Instructions

Search markdown notes across domains, projects, and library.

Case-insensitive substring search with surrounding context lines.

Args:
    query: Search term.
    scope: Where to search -- "all", "domains", "projects", "library".
    limit: Maximum results (default 15).
    max_chars_per_result: Truncate each result's context to this many characters (default 500).
                          Pass 0 for no truncation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
scopeNoall
max_chars_per_resultNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Given no annotations, the description discloses that it performs case-insensitive substring search with context lines and result truncation. However, it does not specify read-only nature, side effects, or permissions.

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 concise, with a one-line summary followed by structured parameter descriptions. No unnecessary words, and the information is efficiently front-loaded.

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?

With an output schema present and moderate complexity, the description covers core functionality well. Minor gaps: does not specify if search is on content or filename, nor the full return structure (handled by output schema).

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?

Despite 0% schema coverage, the description provides clear explanations for all four parameters: query, scope, limit, and max_chars_per_result (including special behavior for 0). Adds value beyond the schema's types and defaults.

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 clearly states it searches markdown notes across specific scopes (domains, projects, library). It distinguishes from many sibling search tools by specifying 'markdown notes' and the supported scopes.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like search_library or search_memory. Lacks context about when to choose this tool over similar ones.

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/SVerITG/Metis'

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