Skip to main content
Glama
disnet
by disnet

get_note_info

Retrieve detailed note information including filenames for link creation in Flint Note's AI-collaborative vault system. Specify note title or filename to access metadata.

Instructions

Get detailed information about a note including filename for link creation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
title_or_filenameYesNote title or filename to look up
typeNoOptional: note type to narrow search
vault_idNoOptional vault ID to operate on. If not provided, uses the current active vault.

Implementation Reference

  • Core handler function that executes the get_note_info tool logic: validates args, searches notes by title_or_filename (optionally filtered by type), and returns structured note info including wikilink format or 'not found' message.
    handleGetNoteInfo = async (args: GetNoteInfoArgs) => {
      // Validate arguments
      validateToolArgs('get_note_info', args);
    
      const { noteManager } = await this.resolveVaultContext(args.vault_id);
    
      // Try to find the note by title or filename
      const searchResults = await noteManager.searchNotes({
        query: args.title_or_filename,
        type_filter: args.type,
        limit: 5
      });
    
      if (searchResults.length === 0) {
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(
                {
                  found: false,
                  message: `No note found with title or filename: ${args.title_or_filename}`
                },
                null,
                2
              )
            }
          ]
        };
      }
    
      // Return the best match with filename info
      const bestMatch = searchResults[0];
      const filename = bestMatch.filename.replace('.md', '');
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              {
                found: true,
                filename: filename,
                title: bestMatch.title,
                type: bestMatch.type,
                path: bestMatch.path,
                wikilink_format: `${bestMatch.type}/${filename}`,
                suggested_wikilink: `[[${bestMatch.type}/${filename}|${bestMatch.title}]]`
              },
              null,
              2
            )
          }
        ]
      };
    };
  • Tool registration in the main MCP server switch statement that routes 'get_note_info' calls to the noteHandlers.handleGetNoteInfo method.
    case 'get_note_info':
      return await this.noteHandlers.handleGetNoteInfo(
        args as unknown as GetNoteInfoArgs
      );
  • Input schema definition for the get_note_info tool provided to MCP clients via ListToolsRequest, defining title_or_filename as required with optional type filter and vault_id.
      name: 'get_note_info',
      description:
        'Get detailed information about a note including filename for link creation',
      inputSchema: {
        type: 'object',
        properties: {
          title_or_filename: {
            type: 'string',
            description: 'Note title or filename to look up'
          },
          type: {
            type: 'string',
            description: 'Optional: note type to narrow search'
          },
          vault_id: {
            type: 'string',
            description:
              'Optional vault ID to operate on. If not provided, uses the current active vault.'
          }
        },
        required: ['title_or_filename']
      }
    },
  • TypeScript interface defining the input arguments for the get_note_info handler.
    export interface GetNoteInfoArgs {
      title_or_filename: string;
      type?: string;
      vault_id?: string;
    }
  • Validation rules used by validateToolArgs('get_note_info', args) to ensure required fields and types before handler execution.
    get_note_info: [
      {
        field: 'title_or_filename',
        required: true,
        type: 'string',
        allowEmpty: false
      },
      {
        field: 'type',
        required: false,
        type: 'string',
        allowEmpty: false
      },
      {
        field: 'vault_id',
        required: false,
        type: 'string',
        allowEmpty: false
      }
    ],
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 mentions 'detailed information' and 'filename for link creation', but doesn't disclose behavioral traits like whether it's read-only (implied by 'get'), error handling, performance, or output format. For a tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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?

Single sentence, front-loaded with core purpose, and efficiently includes key detail about filename. No wasted words; every part earns its place. Structure is clear and appropriately sized for the tool's complexity.

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

Completeness3/5

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

Given no annotations, no output schema, and 3 parameters with full schema coverage, the description is minimally adequate. It states the purpose and a key output aspect (filename), but lacks details on behavior, error cases, or when to use vs. siblings. For a read operation in a complex sibling set, it should provide more context to be fully helpful.

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?

Schema description coverage is 100%, so parameters are fully documented in the schema. The description adds no specific parameter semantics beyond implying 'title_or_filename' is used for lookup and 'filename' is included in output. It doesn't explain parameter interactions or provide extra context, meeting the baseline for high schema coverage.

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 ('Get detailed information') and resource ('about a note'), specifying it includes 'filename for link creation'. It distinguishes from siblings like 'get_note' (likely simpler) and 'get_notes' (list vs. detail), but doesn't explicitly name alternatives. Purpose is specific but could better differentiate from similar tools.

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 vs. alternatives like 'get_note' or 'search_notes'. The description implies it's for detailed info including filenames, but doesn't state prerequisites, exclusions, or compare to siblings. Usage is implied from purpose alone, lacking explicit context.

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/disnet/flint-note'

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