Skip to main content
Glama

Find similar inks

find_similar_inks
Read-only

Find inks similar to one ink, given by name (for example "tsuki-yo" or "Sailor Yama-dori"). basis tells why they are similar: "on_record" for inks InkPalette lists as similar; "color" when none are on record, so these are inks of a close color. match is "closest" when the name was not found as typed, so ink is the closest name.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ink": "<ink>"
    },
    "name": "find_similar_inks"
  }
}

Input Schema

NameRequiredDescriptionDefault
inkYesName of the ink, with or without the brand
limitNoHow many similar inks to return (default 6)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely new behavioral detail: results are labeled with a basis ("on_record" vs "color" fallback when nothing is on record) and a match flag ("closest" when the typed name wasn't found). This discloses the fuzzy-match fallback and result provenance, which an agent could not infer from structured fields alone.

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 purpose is front-loaded in the first clause, and the remaining sentences each explain a distinct output concept (basis, match). The phrasing is somewhat dense and clause-heavy but there is no wasted filler.

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

Completeness4/5

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

With no output schema, the description usefully explains the semantics of the returned basis and match fields, which is the main gap it needed to fill for a simple two-parameter read tool. Missing only explicit sibling routing guidance to be fully complete.

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 coverage is 100%, so the schema already documents both parameters including the "with or without the brand" allowance. The description's example names reinforce the ink parameter's expected form but add little beyond it, and the limit parameter is not mentioned at all.

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 gives a specific verb and resource ("Find inks similar to one ink") plus concrete example inputs, so the tool is identifiable at a glance. It doesn't explicitly differentiate from the sibling find_inks_by_color, which overlaps conceptually with the "color" basis, so it stops short of 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: you supply an ink name and get similar inks. The description explains what the basis values mean, which helps interpret results, but it never states when to choose this tool over find_inks_by_color or search_inks, leaving the routing decision to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources