Skip to main content
Glama
davidgut1982

lore-mcp

by davidgut1982
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

journal_search

Search journal entries by content query, filterable by date range and entry type.

Instructions

Full-text search across journal entry content (Issue #15)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
limitNo
entry_typeNo
date_fromNo
date_toNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

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

  1. Changed20 schema fields changedv0.8.5
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / date_from / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / date_from / default
      Added value: +null
    • removedInput schema / properties / date_from / description
      Removed value: -"ISO date lower bound e.g. 2026-01-01 (optional)"
    • removedInput schema / properties / date_from / format
      Removed value: -"date"
    • removedInput schema / properties / date_from / type
      Removed value: -"string"
    • addedInput schema / properties / date_to / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / date_to / default
      Added value: +null
    • removedInput schema / properties / date_to / description
      Removed value: -"ISO date upper bound (optional)"
    • removedInput schema / properties / date_to / format
      Removed value: -"date"
    • removedInput schema / properties / date_to / type
      Removed value: -"string"
    • addedInput schema / properties / entry_type / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / entry_type / default
      Added value: +null
    • removedInput schema / properties / entry_type / description
      Removed value: -"Filter by entry type (optional)"
    • removedInput schema / properties / entry_type / type
      Removed value: -"string"
    • removedInput schema / properties / limit / description
      Removed value: -"Max results"
    • removedInput schema / properties / limit / maximum
      Removed value: -200
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • removedInput schema / properties / query / description
      Removed value: -"Full-text search query"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}
  2. Addedv0.8.2

TDQS

C2.6/5.0
Behavior2/5

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

The description does not disclose any behavioral traits beyond the basic search operation. Since no annotations are provided, the description should cover aspects like whether it is read-only, pagination, or sorting behavior. It fails to do so.

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

Conciseness3/5

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

The description is a single sentence and thus concise, but it is too brief to be helpful. It lacks structure or prioritization of key information.

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

Completeness1/5

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

Given the schema has 5 parameters with no descriptions and no annotation support, the description is woefully incomplete. It does not explain the search semantics, filtering options, or return format despite the existence of an output schema.

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?

The schema has 0% description coverage, and the tool description adds no meaning to any parameter. It does not explain the purpose of fields like query, limit, entry_type, or date ranges, leaving the agent to infer from names alone.

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 the tool performs full-text search across journal entry content. It uses a specific verb+resource (search across journal entries) and implicitly distinguishes from sibling tools like journal_list and journal_get that serve different purposes.

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 is provided on when to use this tool versus alternatives like search_local or search_corpora. The description does not include any context about prerequisites, exclusions, or comparison with related tools.

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