Skip to main content
Glama

Search inks by name

search_inks
Read-only

Search fountain pen inks by brand or name (for example "iroshizuku" or "pilot kon-peki"). match tells what came back: "exact" for name matches; "color" when no name matched but the query is a color, so these are inks of that color; "closest" when the spelling was off, so inks holds the closest name and similar_inks the inks like it; "none" when nothing was found.

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": {
      "query": "<query>"
    },
    "name": "search_inks"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesBrand and/or ink name, in English or as written on the bottle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 goes well beyond them by enumerating all four match outcomes and explaining which output fields ('inks', 'similar_inks') accompany each. That is exactly the fallback behavior an agent needs to interpret results. It stops short of describing the shape of the returned ink entries, but the match taxonomy is the substantive gap it fills.

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?

Front-loaded with the action, then a compact semicolon-separated enumeration of match values that is easy to scan. Dense but every clause carries information; only minor trimming (e.g. 'so these are inks of that color') would be possible.

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?

One required parameter, no output schema, and the description compensates by explaining the discriminator field that governs how results should be read. A short note on what a single ink entry contains would close the remaining gap, but the critical interpretation logic is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the parameter already documents 'Brand and/or ink name, in English or as written on the bottle'. The description adds value with worked examples showing that either a brand alone or a brand-plus-name string is acceptable input, which the schema does not demonstrate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource ('Search fountain pen inks by brand or name') with two concrete query examples ('iroshizuku', 'pilot kon-peki') that show the brand-only and brand+name forms. An agent can immediately tell this is a text-based ink lookup rather than a color or similarity lookup.

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 only implied: the match semantics reveal that a color query falls back to color results and a misspelling falls back to close names, so an agent can infer this tool tolerates both. However, it never states when to reach for find_inks_by_color or find_similar_inks instead, nor any exclusions.

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