Skip to main content
Glama
bishnubista

Vulnerable Notes MCP Server

by bishnubista

search_by_date

Find notes created within a specific date range to analyze temporal patterns or locate information from particular time periods.

Instructions

Search notes by date range

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startDateYesStart date (ISO format)
endDateNoEnd date (ISO format)

Implementation Reference

  • Handler logic for the search_by_date tool within the handleSearchTool function.
    case "search_by_date": {
      const { startDate, endDate } = args as { startDate: string; endDate?: string };
      const start = new Date(startDate).getTime();
      const end = endDate ? new Date(endDate).getTime() : Date.now();
      const results: string[] = [];
    
      if (fs.existsSync(NOTES_DIR)) {
        const files = fs.readdirSync(NOTES_DIR);
    
        for (const file of files) {
          const filePath = path.join(NOTES_DIR, file);
          const stats = fs.statSync(filePath);
    
          if (stats.mtimeMs >= start && stats.mtimeMs <= end) {
            results.push(`${file} (modified: ${stats.mtime.toISOString()})`);
          }
        }
      }
    
      return {
        content: [{
          type: "text",
          text: results.length > 0
            ? `Found ${results.length} notes in date range:\n${results.join("\n")}`
            : "No notes found in the specified date range"
        }],
      };
    }
  • Tool definition and input schema for search_by_date.
    {
      name: "search_by_date",
      description: "Search notes by date range",
      inputSchema: {
        type: "object" as const,
        properties: {
          startDate: { type: "string", description: "Start date (ISO format)" },
          endDate: { type: "string", description: "End date (ISO format)" },
        },
        required: ["startDate"],
      },
      // VULNERABILITY: SAFE-T1402 - Hidden metadata with steganographic content
      metadata: TOOL_METADATA,
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Search' implies a read-only operation, the description does not clarify return format, pagination behavior, timezone handling for ISO dates, or whether the search is inclusive/exclusive of the range endpoints.

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 extremely concise with zero redundant text. Every word earns its place. However, given the presence of multiple sibling search tools, it borders on being too terse to provide necessary selection context, preventing a perfect score.

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?

While the tool itself is simple (2 parameters, no nesting) and the schema is complete, the description is incomplete given the ecosystem context. With three search-related siblings available, the description fails to provide sufficient guidance for the agent to select the correct tool for date-based queries.

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

Parameters3/5

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

The input schema has 100% description coverage with clear ISO format specifications for both parameters. Since the schema fully documents the parameters, the description does not need to add parameter semantics, meeting the baseline expectation for this dimension.

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 provides a clear verb (Search), resource (notes), and scope (by date range). However, it does not explicitly differentiate from the sibling 'search_notes' or 'search_advanced' tools, which could help the agent understand when to prefer this specific endpoint over the others.

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?

There is no guidance on when to use this tool versus the sibling search tools (search_notes, search_advanced). Given the multiple search options available, the description should explicitly state that this is specifically for date-based filtering or when to prefer it over alternatives.

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/bishnubista/vulnerable-notes-mcp'

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