Skip to main content
Glama

Mecenai

request_viewing

Ask the artist for a viewing of an available artwork. The artist confirms personally.

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": {
      "artwork_id": "<artwork_id>",
      "name": "<name>",
      "email": "<email>"
    },
    "name": "request_viewing"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
emailYes
messageNo
artwork_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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 behavioral burden, and it does disclose one important trait: this submits a request that is confirmed personally by the artist, so it is not an instant booking. It does not explain what happens after submission (notification channel, expected response time), whether repeated submissions create duplicates, or what the caller receives back.

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 sentences, front-loaded with the action and immediately followed by the key behavioral fact. There is no filler, though for a submission tool with three required fields the brevity borders on under-specification rather than pure efficiency.

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

Completeness2/5

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

This is a write/submission tool with no annotations, no output schema, and zero parameter documentation, so the description must compensate for all of it. It conveys the gist but omits return behavior, contact implications of the name/email fields, and confirmation expectations, leaving meaningful gaps for an agent to guess at.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, and the description only gestures at artwork_id by referring to 'an available artwork'; the required name and email fields and the optional message field are never explained. Meaning added beyond the schema is therefore minimal for a tool with three required inputs.

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?

The description names a specific verb and resource: requesting a viewing of an artwork from the artist. The subject matter is clearly distinct from the sibling tools find_artworks and get_price_rule, so an agent can tell what this tool does without opening the schema, though no explicit sibling comparison is made.

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 'of an available artwork' implies a precondition (the artwork must be available), which is useful context for when the tool applies. However, there is no explicit when-to-use guidance, no statement about when it should not be used, and no reference to alternatives such as browsing first with find_artworks.

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.