Skip to main content
Glama

PaintDial

Look up a paint

get_paint
Read-onlyIdempotent

Look up one paint in the PaintDial library by name or code and return its brand, name, code, published colour value and PaintDial page.

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": {
      "colour": "<colour>"
    },
    "name": "get_paint"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoOptional. The brand, if the name is used by more than one brand.
colourYesThe paint name or code, for example "Skimming Stone".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds value by enumerating what is returned (brand, name, code, published colour value, PaintDial page), which matters because there is no output schema. It stops short of describing not-found or ambiguous-name behavior, though the brand parameter hints that ambiguity is possible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence that front-loads the action, the source library, and the lookup keys, then closes with the return fields. No filler or redundancy.

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 two-parameter, read-only lookup with full schema coverage and rich annotations, the description is essentially complete, including return values in lieu of an output schema. The only real gap is error/empty-result behavior and how ambiguity between name and code is handled.

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 description coverage is 100%, so baseline is 3. The phrase "by name or code" reinforces that colour accepts either form, and "one paint" signals single-result semantics, but nothing is added about how brand resolves collisions beyond what the schema already says.

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 and resource ("Look up one paint in the PaintDial library") plus the lookup keys (name or code) and the returned fields. It clearly reads as a single-item lookup, implicitly distinct from the sibling's nearest-match search, but never names or contrasts with that sibling.

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?

The phrase "Look up one paint" implies the when-to-use case (resolving a known paint) versus a discovery/search operation, but the description never states when to prefer it over find_closest_paints or what to do if the paint is unknown. Usage must be inferred from the tool name and the word "one".

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