Skip to main content
Glama

Get ink details

get_ink_details
Read-only

Describe one ink: a summary, how it writes (flow, dry time, shading, sheen, water resistance), shimmer, iron gall, good uses, its swatch, writing samples people posted, reviews, similar inks, and its page on inkpalette.co. match is "closest" when the name was not found as typed, so this 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": "get_ink_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
inkYesName of the ink, with or without the brand
languageNoLanguage of the summary (default en)

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 already cover read-only and open-world safety, so the description is free to add the non-obvious part: results aggregate external sources (writing samples people posted, reviews, an inkpalette.co page) and name resolution is fuzzy, with a "match" value of "closest" signaling that a returned ink may not be the exact name typed. That fallback disclosure is genuinely useful and prevents an agent from treating a near-match as authoritative. Auth, rate limits and response envelope remain unstated.

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 long field enumeration is informative rather than padding, since no output schema exists to convey the return shape. The trailing sentence about "closest" is slightly awkwardly attached but still earns its place.

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 correctly takes on the burden of describing what comes back, and it does so field by field, including the derived similar-inks and external-page sections. The one real gap is what happens when nothing resembling the name exists, but the match semantics cover the most likely confusion.

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% and the schema already explains that ink may be given with or without the brand and that language defaults to en. The description adds nothing about the language parameter and only obliquely touches the ink parameter via the failed-exact-match scenario, so the schema carries the load and baseline 3 applies.

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?

"Describe one ink" gives a specific verb and a singular resource, and the enumerated field list (summary, flow, dry time, shading, sheen, shimmer, iron gall, swatch, samples, reviews, similar inks, page) makes the scope unmistakable. It never names a sibling, so the agent must infer that detail lookup by name differs from search_inks or find_inks_by_color rather than being told.

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: an agent gathers that this is the lookup performed once an ink name is known. There is no explicit "use this when / not when" and no named alternative, even though find_similar_inks and search_inks overlap in subject matter. The fuzzy-match note is behavioral, not selection guidance.

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