Graffiticode

Create interactive content in any Graffiticode language. Describe what you want in natural language — a language-specific AI generates the result. Call list_languages() first to discover available languages, then pass the language ID here. Your closest match is good enough — the platform validates it against the language's scope and re-routes the request if another language fits better. The description should be a natural language request, not code, written in English. Be specific about the content, structure, layout, theme, and any assessment or interaction requirements. Only the description itself must be English — content you want to appear in the item (vocabulary, names, passages) may be in any language. To reuse content from an existing item (any language) — e.g. "make this spreadsheet into a Learnosity question" — call get_spec(item_id) and use its returned text as this description, adding only your intent/target framing. Never paste another item's src/data or its id, and do not name upstream languages or wire a pipeline: just describe what you want and let the generator identify the languages and compose. Generation runs asynchronously: this returns immediately with an item_id and status "generating". Call render_item(item_id) to retrieve and display the result. What this does and doesn't do: it authors content in the user's Graffiticode workspace only. The platform routes the request to the best-fitting language and may compose languages for one item (e.g. a Learnosity item with an embedded spreadsheet). It never writes to an external system — in particular it never saves to a Learnosity item bank; the user does that from the item's page in the Graffiticode console. Its only outward effect: a fetch-and-shape-data item reads the public HTTPS URLs it names.

create_item

Get an existing Graffiticode item by ID. Returns the item's raw data, code, and metadata for programmatic clients. Prefer render_item for normal user-facing retrieval because it keeps the language-private src/data out of the model transcript while still rendering supported widgets. If generation is still running, this waits for completion and returns status "ready", "generating", or "failed". The returned src and data are PRIVATE to this item's language — do not pass them to another language's create_item; to move this content to a different language, call get_spec(item_id) instead.

get_item

Get a precise, platform-neutral English specification of an existing item's content. Call this FIRST whenever the user gives you a Graffiticode item — its id, or a link such as https://app.graffiticode.org/form/<item_id> (the id is the last path segment) — and asks to reuse, recreate, convert, copy, or turn it into something else. An item id is exactly this tool's input: never tell the user an id is not enough or ask them for a screenshot of the item — fetch its content here. Use the result to reproduce or wrap the item's content in ANOTHER language: pass the returned spec as the create_item description for the target language. The spec captures every authored detail (questions, options, answer keys, formulas, passages) with no language-specific encoding. Never pass an item id or get_item output (src/data) to create_item — those are private to the item's own language and another language's generator cannot interpret them. get_spec is the only correct way to move content across languages.

get_spec

Get detailed authoring information about a Graffiticode language. Returns an inline authoring_guide summary, supported_item_types, example_prompts, and a user_guide_resource URI (readable via ReadResource for the full markdown guide). Usually sufficient to compose a good create_item request. Call this after list_languages() to learn about a specific language before using create_item().

get_language_info

Discover available Graffiticode languages. Use this to find a language that matches the user's needs. The catalog is dynamic and grows over time. Use the search parameter to match by keyword (e.g., "spreadsheet", "flashcard", "chart"), or the domain parameter to narrow to a domain (e.g., "assessments"). Returns language IDs, names, descriptions, domain memberships, and a `when_to_use` steering note. Read `when_to_use` before choosing: it states the conditions a language requires and, where one exists, the gate that rules it out. Honor its negative clauses — a language that says "do NOT use for X" must not be chosen for X, however well its question types or item types seem to match. If nothing in the returned set fits the request, say so and ask the user rather than forcing the closest match.

list_languages

Retrieve and display an existing Graffiticode item by ID. This is the preferred retrieval tool after create_item or update_item. It waits for generation to complete and returns compact status and identity fields; supported hosts receive the full language-private rendering payload separately as widget metadata, keeping source code, compiled data, and answer keys out of the model transcript. Use get_item only when the caller explicitly needs raw src/data for programmatic work.

render_item

Modify an existing Graffiticode item by describing what to change in natural language. This replaces the item's current content in place — the previous version cannot be restored through the assistant, so treat each update as an overwrite. The language is auto-detected from the item. Conversation history is preserved, so you can make incremental changes: "add another concept", "change the theme to dark", "make the header row blue". Write the modification in English, as with create_item; content destined for the item itself may be in any language. Like create_item, generation runs asynchronously: this returns immediately with status "generating". Call render_item(item_id) to retrieve and display the updated result.

update_item