Skip to main content
Glama

Ink of the day

ink_of_the_day
Read-only

One fountain pen ink for today, the same for everyone on the same day (UTC), with its swatch and its page on inkpalette.co.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ink_of_the_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 declare readOnlyHint and openWorldHint, so the bar is lower, yet the description adds real value: the result is identical for all users on a given UTC day, and it includes a swatch and a link to the ink's page on inkpalette.co. It does not mention caching/rollover behavior at UTC midnight, which would have completed the picture.

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?

A single tight sentence with no filler. The determinism clause is front-loaded, though the trailing "with its swatch and its page on inkpalette.co" reads slightly loosely rather than as a crisp statement of what is returned.

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?

For a zero-required-parameter, read-only tool with no output schema, the description covers the essentials: what is returned (an ink plus swatch and page link) and the determinism rule. The only gap is the optional language parameter's effect, a minor omission.

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 single optional language enum is fully documented in the schema, so the baseline applies. The description never mentions that the response language can be switched or that an English summary is the default, so it adds nothing beyond the schema here.

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?

"One fountain pen ink for today, the same for everyone on the same day (UTC)" names a specific resource and scope — a deterministic daily pick — which is clearly distinct from the sibling search/details tools. It is framed as a noun phrase rather than an explicit verb, but the operation and result are unambiguous.

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 rather than stated: an agent can infer this is for "what's today's ink" questions and that search_inks or get_ink_details cover other needs. There is no explicit when-to-use/when-not-to-use or sibling routing statement.

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