Rolli MCP

update_agent_run

Rename or pin a Rolli Agent run by updating its metadata; supply a label or pinned status to organize and manage runs.

Instructions

Update a Rolli Agent run's metadata (rename or pin). At least one of pinned or label is required.

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": {
      "id": "<id>"
    },
    "name": "update_agent_run"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Run UUID
`label`	No	Custom label (e.g., "Weekly trend report")
`pinned`	No	Pin or unpin the run

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.5.0Nov 4, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / id / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

Addedv1.3.0Jun 3, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It does add one genuinely useful constraint the schema does not encode (no anyOf/oneOf enforcing at least one of pinned/label), but it omits permission requirements, whether label overwrites or clears, and whether the update is idempotent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, no filler, with the resource and the allowed operations front-loaded ahead of the precondition. Every clause earns its place.

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

Completeness3/5

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

For a three-parameter mutation tool with no annotations and no output schema, the definition is minimally viable. The schema covers the parameters well, but the description leaves the agent guessing about side effects, permissions, and what a successful update returns.

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 the schema already documents id, label, and pinned. The description adds only the cross-parameter requirement that at least one of pinned or label be present, which is real value but limited; nothing is said about label length, empty-string semantics, or pinning behavior.

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?

States a specific verb and resource ("Update a Rolli Agent run's metadata") and narrows the scope with "(rename or pin)", which lets an agent separate it from get_agent_run, delete_agent_run, and cancel_agent_run. It stops short of naming a sibling or stating what the tool does NOT do.

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

Usage Guidelines2/5

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

The only conditional guidance is a precondition ("At least one of pinned or label is required"), not a when-to-use rule. There is no indication of when to choose this over adjacent tools such as update_agent_schedule or rerun_agent_run, and no exclusions.

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