Skip to main content
Glama
davidgut1982

lore-mcp

by davidgut1982
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

search_local

Search local files for specific content using lexical matching. Find relevant files by query, optionally restricted to paths or file types.

Instructions

Search local files by content (lexical mode)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
pathsNo
file_typesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed13 schema fields changedv0.8.5
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / file_types / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / file_types / default
      Added value: +null
    • removedInput schema / properties / file_types / description
      Removed value: -"File extensions to search (default: txt, json, md, py, yaml)"
    • removedInput schema / properties / file_types / items
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / file_types / type
      Removed value: -"array"
    • addedInput schema / properties / paths / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / paths / default
      Added value: +null
    • removedInput schema / properties / paths / description
      Removed value: -"Paths to search (defaults: learning, xtts, knowledge)"
    • removedInput schema / properties / paths / items
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / paths / type
      Removed value: -"array"
    • removedInput schema / properties / query / description
      Removed value: -"Search query"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}
  2. First observedv0.7.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'search local files by content', implying read-only, but no details on permissions, rate limits, or side effects. Missing key behavioral context.

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

Conciseness2/5

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

Extremely brief but at the cost of informativeness. A single phrase does not convey enough detail for a tool with multiple parameters and siblings.

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

Completeness2/5

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

Given 3 parameters (one required) and no parameter descriptions or behavioral annotations, the description is insufficient. Output schema exists but is not referenced. Agent lacks context for correct invocation.

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

Parameters1/5

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

Schema coverage is 0%, yet the description provides no parameter details. The 'query', 'paths', and 'file_types' parameters are left unexplained, forcing the agent to infer their meaning from names alone.

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 states the action (searching local files) and mode (lexical), distinguishing it from semantic search or other search tools. However, 'lexical mode' is not explained, mildly reducing clarity.

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 guidance on when to use this tool versus many sibling search tools like 'search_corpora', 'kb_search', or 'multi_search'. The description does not provide context for appropriate use.

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/davidgut1982/lore-mcp'

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