Skip to main content
Glama
ewilderj

Fountain Pen Ink MCP Server

get_inks_by_maker

Retrieve fountain pen inks from a specific manufacturer to explore available colors and properties for selection.

Instructions

List all inks from a specific manufacturer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
makerYesManufacturer name (e.g., "sailor", "diamine")
max_resultsNoMaximum number of results to return (default: 50)

Implementation Reference

  • The main handler function that executes the tool logic: filters ink search data by maker name (case-insensitive), retrieves corresponding color data, creates search results, and returns formatted JSON response.
    private getInksByMaker(maker: string, maxResults: number): MCPTextResponse {
      const makerLower = maker.toLowerCase();
      const makerInks = this.inkSearchData
        .filter((item) => item.maker.toLowerCase() === makerLower)
        .slice(0, maxResults);
    
      const results: SearchResult[] = [];
    
      for (const metadata of makerInks) {
        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(
              {
                maker,
                results_count: results.length,
                results,
              },
              null,
              2,
            ),
          },
        ],
      } satisfies MCPTextResponse;
    }
  • src/index.ts:192-210 (registration)
    Tool registration in ListToolsRequest handler, defining the tool name, description, and input schema (maker: string required, max_results: number optional default 50).
    {
      name: 'get_inks_by_maker',
      description: 'List all inks from a specific manufacturer',
      inputSchema: {
        type: 'object',
        properties: {
          maker: {
            type: 'string',
            description: 'Manufacturer name (e.g., "sailor", "diamine")',
          },
          max_results: {
            type: 'number',
            description: 'Maximum number of results to return (default: 50)',
            default: 50,
          },
        },
        required: ['maker'],
      },
    },
  • Dispatcher case in CallToolRequest handler that routes the tool call to the getInksByMaker implementation with argument parsing.
    case 'get_inks_by_maker':
      return this.getInksByMaker(
        args.maker as string,
        (args.max_results as number) || 50,
      );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but only states the basic function. It doesn't mention whether this is a read-only operation, what format results are returned in, whether there are rate limits, authentication requirements, or any error conditions. For a tool with no annotation coverage, this leaves significant behavioral questions unanswered.

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 gets straight to the point with zero wasted words. It's appropriately sized for a simple listing tool and front-loads the essential information.

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?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what format the results will be in, whether there's pagination, what happens when no inks are found for a manufacturer, or any error handling. The context signals show this is a simple tool, but the description should still address basic behavioral expectations.

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 schema description coverage is 100%, so both parameters are already documented in the schema. The description mentions 'from a specific manufacturer' which aligns with the 'maker' parameter, but adds no additional semantic context beyond what the schema already provides. This meets 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 verb 'List' and resource 'inks from a specific manufacturer', making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'search_inks_by_name' or 'search_inks_by_color' - all could potentially list inks, just with different filtering criteria.

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. With sibling tools like 'search_inks_by_name', 'search_inks_by_color', and 'get_ink_details' available, there's no indication of when this manufacturer-focused listing is preferred over other search methods or when it might be inappropriate.

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