Skip to main content
Glama

Translate taste words into decisions

ihumane_translate_taste
Read-only

Call this when your human describes the look, feel or voice with taste words ('clean', 'modern', 'premium', 'playful', 'make it pop', 'friendly', 'professional', 'sounds robotic') or feeling words ('exciting', 'amazing', 'wow', 'make people excited'). Returns the concrete decisions those words usually mean. Say your translation back to the human in one line BEFORE building or writing, so a wrong reading costs nothing.

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": {
      "words": "<words>"
    },
    "name": "ihumane_translate_taste"
  }
}

Input Schema

NameRequiredDescriptionDefault
wordsYesThe human's words, as they wrote them, e.g. 'clean and modern' or 'make it more friendly'

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 already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description still adds substantive behavior by saying the result is an interpretation of what words usually mean and should be surfaced to the human before action so a misreading is cheap. It does not discuss input limits (the 300-char cap lives only in the schema) or output shape, but the added process guidance is real value beyond the annotations.

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?

Three sentences ordered as trigger, return, and process, with the trigger front-loaded. The long parenthetical example lists are verbose but earn their place by disambiguating a fuzzy judgment call, and no sentence is pure 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?

For a one-parameter, read-only helper with no output schema, the agent learns what to send, what kind of answer to expect, and what to do with it before acting. The absence of any return-format detail is a minor gap given no output schema exists to cover it.

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?

With a single parameter at 100% schema coverage, the schema already explains that 'words' takes the human's verbatim phrasing. The description's example vocabulary loosely signals what to pass, but it adds no format, quoting, or paraphrase rules beyond the schema's own 'as they wrote them' wording.

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?

The description names a specific verb and resource: it translates taste/feeling words into concrete decisions, and it enumerates the exact trigger vocabulary ('clean', 'modern', 'make it pop', 'sounds robotic'). That trigger list makes it unmistakable which inputs belong here rather than to the review, feedback, or rules siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The opening clause gives an explicit when-to-use condition with concrete examples, and the final sentence adds a workflow rule: echo the translation back in one line BEFORE building or writing. It does not name an alternative tool or state when not to call it, which is the only gap.

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