Skip to main content
Glama

Mecenai

find_artworks

Find artworks by series name or artwork title (partial match). Facts only, no prices.

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": {
      "query": "<query>"
    },
    "name": "find_artworks"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose two useful behavioral traits: matching is partial (not exact) and results exclude price data. It says nothing about result caps, pagination, ordering, or whether the search is case-sensitive, which matters for an unannotated read tool driven by a free-text query.

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?

Two short sentences, no filler, with the primary capability front-loaded and the output-scope caveat second. Every clause carries information.

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?

The tool is simple — one required string parameter and an output schema that documents returns — so the description need not explain response shape. What remains missing (result limits, pagination, tie-breaking) is modest but real for an unannotated search endpoint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the schema offers only a bare 'Query' string, so the description must compensate. It does so reasonably well by defining the query as a series name or artwork title and flagging partial matching, which is the key detail an agent needs; it does not specify format, escaping, or minimum length.

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?

Names a specific verb and resource (find artworks) and specifies the two searchable dimensions (series name or artwork title) plus the match mode (partial). The clause 'Facts only, no prices' implicitly separates it from get_price_rule, though it never names that sibling explicitly.

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 the lookup to use when it has a series or title string, and that pricing must be sought elsewhere. There is no explicit when-not guidance, no mention of what to do with ambiguous or empty matches, and no routing to request_viewing.

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.