Skip to main content
Glama

lqd_verdict

An independent yes-or-no style verdict, with a short reason, on a men's clothing item or outfit. Called by an agent before purchase. No affiliate cut, no placement fees. Use when an agent is about to buy menswear: call before checkout for a YES, NO, or OPTIONS verdict.

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": {
      "description": "<description>"
    },
    "name": "lqd_verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNo
optionsNoIf set, LQD picks one (OPTIONS).
recipientNoOptional one-line style note for a gift check, such as classic daytime clothes and loafers. Same price. LQD does not treat this as a wardrobe.
example_idNoOptional caller id for this example. Echoed back. Not required.
image_pathNo
descriptionYesPiece or look, comma-separated pieces work best (color, fabric, shoe). For a gift check, this is the gift.
product_urlNo
previous_verdict_idNoOptional id of an earlier verdict. Echoed back. Not required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"Piece or look, comma-separated pieces work best (color, fabric, shoe)."New value: +"Piece or look, comma-separated pieces work best (color, fabric, shoe). For a gift check, this is the gift."
    • addedInput schema / properties / recipient
      Added value: +{
      +  "description": "Optional one-line style note for a gift check, such as classic daytime clothes and loafers. Same price. LQD does not treat this as a wardrobe.",
      +  "maxLength": 240,
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / example_id
      Added value: +{
      +  "description": "Optional caller id for this example. Echoed back. Not required.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / previous_verdict_id
      Added value: +{
      +  "description": "Optional id of an earlier verdict. Echoed back. Not required.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose useful traits: the return is a verdict plus a short reason, it is independent, and there are no affiliate/placement incentives. It says nothing about latency, cost, whether image_path/product_url are actually consumed, or error behavior, which are real gaps for an unannotated tool.

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?

Two short, front-loaded sentences with the core purpose first and the usage trigger second. The 'No affiliate cut, no placement fees' line is mildly promotional but does convey the independence of the verdict, so it mostly earns its place.

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

Completeness3/5

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

The description conveys the output (a verdict with a reason), which is needed since there is no output schema. For an 8-parameter tool with a nested 'context' object and three undocumented parameters, however, it leaves the agent guessing about how to supply images, URLs, or context correctly.

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 63%, so the description needs to compensate for context, image_path, and product_url, which it does not explain at all. It does add meaning for 'options' (triggers an OPTIONS verdict), 'recipient' (gift check, not a wardrobe), and 'description' (comma-separated pieces), but these largely restate schema text. Baseline 3 is appropriate given the partial coverage and the undocumented nested context object.

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?

States a specific verb+resource: an independent yes-or-no verdict with a short reason on a men's clothing item or outfit. It also names the result shapes (YES, NO, OPTIONS), so the agent knows exactly what it gets back. There are no siblings to differentiate from, so a 4 rather than 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 Guidelines4/5

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

Explicitly says to call it 'before checkout' when 'an agent is about to buy menswear', which gives a clear trigger condition. It stops short of when-not-to-use guidance or prerequisites (e.g., minimum input, cost, rate limits), so it is not a full 5.

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