Skip to main content
Glama
ewilderj

Fountain Pen Ink MCP Server

get_ink_details

Retrieve comprehensive details about a specific fountain pen ink using its unique identifier to access color information and specifications.

Instructions

Get complete information about a specific ink

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ink_idYesThe unique identifier for the ink

Implementation Reference

  • The primary handler function implementing the get_ink_details tool logic. It looks up the ink by ID in the loaded inkColors and metadata arrays, generates a detailed result using createSearchResult, computes hex color, family, and description, and returns a formatted MCPTextResponse.
    private getInkDetails(inkId: string): MCPTextResponse {
      const inkColor = this.inkColors.find((ink) => ink.ink_id === inkId);
      const metadata = this.getInkMetadata(inkId);
    
      if (!inkColor) {
        throw new Error(`Ink not found: ${inkId}`);
      }
    
      const result = createSearchResult(inkColor, metadata);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              {
                ink_details: result,
                hex_color: rgbToHex(inkColor.rgb), // Now actually RGB!
                color_family: getColorFamily(inkColor.rgb),
                color_description: getColorDescription(inkColor.rgb),
              },
              null,
              2,
            ),
          },
        ],
      } satisfies MCPTextResponse;
  • src/index.ts:178-191 (registration)
    Tool registration entry in the ListToolsRequestSchema handler, defining the tool name, description, and input schema for get_ink_details.
    {
      name: 'get_ink_details',
      description: 'Get complete information about a specific ink',
      inputSchema: {
        type: 'object',
        properties: {
          ink_id: {
            type: 'string',
            description: 'The unique identifier for the ink',
          },
        },
        required: ['ink_id'],
      },
    },
  • Input schema definition for the get_ink_details tool, specifying the required 'ink_id' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        ink_id: {
          type: 'string',
          description: 'The unique identifier for the ink',
        },
      },
      required: ['ink_id'],
    },
  • Dispatch handler in the CallToolRequestSchema switch statement that routes calls to get_ink_details to the private getInkDetails method.
    case 'get_ink_details':
      return this.getInkDetails(args.ink_id as string);
  • Helper method used by getInkDetails to retrieve search metadata for the ink by ID.
    private getInkMetadata(inkId: string): InkSearchData | undefined {
      return this.inkSearchData.find((item) => item.ink_id === inkId);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is to 'Get' information, implying a read-only operation, but doesn't specify aspects like authentication requirements, rate limits, error handling, or what 'complete information' entails (e.g., fields returned). This is a significant gap for a tool with zero annotation coverage.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized for a simple tool, though it could be slightly more informative without losing conciseness.

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 incomplete. It doesn't explain what 'complete information' includes (e.g., properties like color, maker, or viscosity), nor does it cover behavioral aspects like response format or potential errors. This leaves the agent with insufficient context to use the tool effectively.

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 the 'ink_id' parameter clearly documented as 'The unique identifier for the ink'. The description adds no additional meaning beyond this, such as format examples or constraints. Given the high schema coverage, a baseline score of 3 is appropriate as 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 verb ('Get') and resource ('complete information about a specific ink'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_inks_by_maker' or 'search_inks_by_name', which might also retrieve ink information but with different scopes or filters.

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 prerequisites like needing an ink_id, nor does it contrast with siblings such as 'get_inks_by_maker' for batch retrieval or 'search_inks_by_name' for fuzzy matching. This leaves the agent without context for tool selection.

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