Skip to main content
Glama

describe_drawing

Read-onlyIdempotent

Get the exact drawing format and style guidance, with examples when available, for a character, object, or place before using a draw tool.

Instructions

Read-only: the exact drawing format for draw_character, draw_object or draw_place in the current style (or the style given), with the look the style wants and an example when it has one. Read it before drawing. It describes the format, not a shot: to see a shot use look; for the project format use how_to.

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": {
      "kind": "<kind>"
    },
    "name": "describe_drawing"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhich draw tool you're about to use.
styleNoA style id. Default: the project's style.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / kind / description
      Added value: +"Which draw tool you're about to use."
    • addedInput schema / properties / style / description
      Added value: +"A style id. Default: the project's style."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds value beyond that by disclosing what the response contains — the style's desired look and an example when one exists — plus a negative clarification that it does not return a shot. Slightly redundant in restating 'Read-only', which keeps it from a 5.

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 short sentences, front-loaded with the read-only scope and the core purpose before the routing hints. Each sentence carries information, though the phrase 'with the look the style wants and an example when it has one' is slightly loose and could be tighter.

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 tool with rich annotations and no output schema, the description covers purpose, timing, alternatives and roughly what comes back. Only the exact shape of the returned format/example is left implicit, which is a minor gap for a pre-drawing reference lookup.

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 100%, so both parameters and the style default are already documented in structured fields. The description only echoes the current-vs-given style distinction and implies kind selects which draw tool, adding no format or syntax detail beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource: it returns the exact drawing format for draw_character, draw_object or draw_place, in the current or given style. It also distinguishes itself from siblings by naming look (a shot) and how_to (project format), so an agent can separate it from adjacent read tools without opening schemas.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Read it before drawing') and explicit exclusions with named alternatives: 'to see a shot use look; for the project format use how_to.' This is when/when-not/alternative routing in a compact form.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.