Skip to main content
Glama
ewilderj

Fountain Pen Ink MCP Server

search_inks_by_name

Find fountain pen inks by name using fuzzy search to match partial or similar ink names in the database.

Instructions

Search for fountain pen inks by name using fuzzy matching

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch term for ink name
max_resultsNoMaximum number of results to return (default: 20)

Implementation Reference

  • The main handler function that executes fuzzy name search using Fuse.js on ink metadata, matches with color data, formats results with createSearchResult helper, and returns structured JSON response.
    private searchInksByName(query: string, maxResults: number): MCPTextResponse {
      const searchResults = this.fuse.search(query);
      const results: SearchResult[] = [];
    
      for (const result of searchResults.slice(0, maxResults)) {
        const metadata = result.item;
        const inkColor = this.inkColors.find((ink) => ink.ink_id === metadata.ink_id);
    
        if (inkColor) {
          results.push(createSearchResult(inkColor, metadata));
        }
      }
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              {
                query,
                results_count: results.length,
                results,
              },
              null,
              2,
            ),
          },
        ],
      } satisfies MCPTextResponse;
    }
  • JSON schema defining the input parameters for the tool: query (string, required) and max_results (number, optional default 20).
    inputSchema: {
      type: 'object',
      properties: {
        query: {
          type: 'string',
          description: 'Search term for ink name',
        },
        max_results: {
          type: 'number',
          description: 'Maximum number of results to return (default: 20)',
          default: 20,
        },
      },
      required: ['query'],
    },
  • src/index.ts:140-158 (registration)
    Tool registration in the ListTools response, including name, description, and input schema.
    {
      name: 'search_inks_by_name',
      description: 'Search for fountain pen inks by name using fuzzy matching',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'Search term for ink name',
          },
          max_results: {
            type: 'number',
            description: 'Maximum number of results to return (default: 20)',
            default: 20,
          },
        },
        required: ['query'],
      },
    },
  • src/index.ts:271-275 (registration)
    Handler routing in the CallToolRequestSchema switch statement that invokes the searchInksByName method.
    case 'search_inks_by_name':
      return this.searchInksByName(
        args.query as string,
        (args.max_results as number) || 20,
      );
  • Helper function used in the handler to format each search result with ink data, metadata, distance, and URLs to details/images.
    export function createSearchResult(
      ink: InkColor,
      metadata?: InkSearchData,
      distance?: number,
    ): SearchResult {
      return {
        ink,
        metadata,
        distance,
        url: `https://wilderwrites.ink/ink/${ink.ink_id}`,
        image_url: `https://wilderwrites.ink/images/inks/${ink.ink_id}-sq.jpg`,
      };
    }
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. It mentions 'fuzzy matching' but doesn't explain how it works, what the output format is, or any limitations like rate limits or authentication needs. For a search tool with no annotations, this is a significant gap in transparency.

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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 the lack of annotations and no output schema, the description is incomplete. It doesn't explain what the search results look like, how fuzzy matching behaves, or any error conditions. For a search tool with two parameters and no structured output, more context is needed 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?

The input schema has 100% description coverage, with clear documentation for both parameters ('query' and 'max_results'). The description adds no additional parameter details beyond what the schema provides, such as examples or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 tool's purpose: 'Search for fountain pen inks by name using fuzzy matching.' It specifies the verb (search), resource (fountain pen inks), and method (fuzzy matching by name). However, it doesn't explicitly differentiate from sibling tools like 'search_inks_by_color' or 'get_inks_by_maker', which is why it's not a 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'search_inks_by_color' or 'get_ink_details', nor does it specify any prerequisites or exclusions. This leaves the agent without clear usage 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/ewilderj/inks-mcp'

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