Skip to main content
Glama

Axad

Get a picture

nominate_image

Ask for a picture of a generic concept every learner shares: a concrete thing, action, place or everyday scene. Returns an existing library picture when one stands for the concept; otherwise checks the request against the library's rules and draws a new one, which fills in when ready (this spends credit). canon names the concept in 1 to 4 English words.

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": {
      "title": "<title>",
      "concept": "<concept>",
      "canon": "<canon>",
      "lang": "<lang>",
      "prompt": "<prompt>"
    },
    "name": "nominate_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
langYesBCP 47 code of the concept.
textNoOnly when words in the picture are the lesson: at most 6 words in `lang`, also written in the prompt in double quotes. Omit it for a picture with no words, which serves every language.
canonYesThe generic English concept the picture shows, 1–4 words, dictionary form, with no names, numbers or words of one sentence: "doctor's practice", "apple", "train platform". The library keeps one picture per canon.
titleYesOne literal English sentence of 8–40 words: who, what, where. Generic, with no names, numbers, clock times or dates. Search reads it.
promptYesWhat to draw, 40–200 English words: the scene, each object and where it is, what the people do. Concrete, drawable and generic: no names, clock times, dates or numbers (except quoted `text`); no style words.
conceptYesThe language element it teaches, 1–8 words in its language: "cancelar", "la sala de espera". The `image` fields that show this picture hold these words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=false, so the agent knows this is a bounded, non-read-only operation. The description adds real value by disclosing that an existing library picture may be returned, that a new one is drawn only after a rule check, that generation is asynchronous ('fills in when ready'), and that it spends credit. That is strong context beyond the annotations, though it omits what a result looks like before it is ready.

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 sentences that front-load the purpose and then the resolution path and cost; the parenthetical credit note is compact. Minor awkwardness in 'which fills in when ready' but no filler.

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 generation-capable tool with no output schema, the description covers the key operational facts: library reuse, rule validation, asynchronous completion, and credit spend. It stops short of describing what the caller receives while the picture is pending, which is the main remaining gap.

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 every parameter is already documented in detail. The description only restates the canon constraint (1 to 4 English words) and adds no syntax or interaction details beyond the schema, so baseline 3 applies.

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 uses a concrete verb and resource ('Ask for a picture of a generic concept') and explains the two modes of resolution (library lookup vs. newly drawn). It does not explicitly name a sibling such as find_images or show_picture, so differentiation from them is left to inference.

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 'a generic concept every learner shares' implies when this tool is appropriate (generic, shareable imagery) and the credit note hints at a cost trade-off. However, there is no explicit when-not guidance and no routing to alternatives like find_images for existing imagery.

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.