# Agents that work in batches, and sign what they decide.

1 October 2026 · By the Nodary team

Over MCP, an agent now creates 25 documents or changes 50 in one call, reads the week’s activity, sends and fetches files, sees a board as people do and starts from ready-made prompts. Each decision it makes carries your name.

![Saltmarrow, a fictional sample project, on Nodary’s constellation map: documents around hubs for Vision, World and story, Characters, Systems, Production, Localisation, Audio and Art direction, with two teammates’ cursors. An agent connected over MCP reads and changes the same project](https://nodary.ai/release-media/2026-10-agents-project-map.webp)

An agent connected to Nodary over MCP could read and write documents one at a time. A studio’s agent needs more: turn twenty playtest notes into tasks, see who has what before a stand-up, pass a concept to an image tool and bring the result back. This release gives it the tools for that, and keeps every write accountable.

## Batches, and the producer’s view

create_stars makes up to 25 documents in one call, each filled, filed, tagged, dated, assigned and linked. update_stars changes up to 50, add_comments leaves up to 20 notes, and update_pictures decides up to 50 pictures across 20 documents. Each item comes back done, or with the reason it was not. list_stars now gives the assignee, the due date and the review state, and filters by who has it, lateness and blockers. recent_changes returns what happened, not only what was saved: statuses, assignments, moves, renames, reviews, picture decisions, comments, and documents deleted or restored, with a cursor to page back.

## Files in and out

start_upload gives an agent an address to send its own file to, such as a render, a video, a sound, a glTF model or a .psd, and add_image or add_media places it in a document once Nodary has checked it is what it claims to be. get_file_url gives a 15-minute link to any file of a document, so a picture can go to an image generator or a model to a 3D tool, and come back. render_board shows the agent a board, or one of its frames, as people see it, and get_image shows a picture with the notes drawn on it.

## A protocol programs can rely on

Four prompts start common work from one request: What changed this week, Review the art, Turn playtest notes into tasks, and Review a loot table or a curve. Two resources let a client attach a document or a project outline by address. Clients on the 2025-06-18 version of the protocol get structured results with error codes they can act on, every 429 says when to come back with Retry-After, and the tool catalogue is lighter, with block formats read on demand through describe_blocks. Writes take a retry key: repeat a call with the same key after a timeout and the first answer comes back, never a duplicate.

## Accountable by design

A decision an agent makes is signed with the name of the person whose key it uses, and rewriting a document can never write or sign one. A key limited to one project now stays in it, even when listing or creating projects. Several tool calls sent in one request count one by one, five at most. Connect by signing in from your MCP client, or with an API key.

## Try it in your workflow

1. Add Nodary’s MCP address to your client and sign in.
2. Run the What changed this week prompt on your project.
3. Ask the agent to turn your playtest notes into tasks with create_stars, assigned and dated.
4. Find them on the map, then ask recent_changes what moved this week.

MCP is a paid add-on, for one member or the whole team. A request carrying more than five tool calls is refused, an upload is up to 50 MB (250 MB for a plain file), and a file link expires after 15 minutes. An agent cannot yet export a whole project in one call nor check that a diagram renders, and nothing syncs with Jira, Linear or GitHub. The example link opens the MCP documentation, with every tool and how to connect.

The page: https://nodary.ai/updates/agents-work-in-batches-and-sign-their-decisions