Skip to main content
Glama

Update Exploratory Session

update_session
Destructive

Modify an existing exploratory session by sending only changed fields, or permanently close it when the user requests; closing freezes the session and cannot be reopened through MCP.

Instructions

Modify an existing exploratory session, or close it. Closing is permanent: send updates.status="closed" only when the user asks to close the session, never as part of another edit. Send only fields you want to change inside the updates object. Requires write permission. Allowed fields: name, mission, sessionType, config, environment, releaseId, assigneeUserId, state, estimate, tags, linkedIssues. Closing works like the UI "Close session" button: it freezes the session and snaps state to the project's "Done" option; MCP cannot reopen it. Files cannot be added over MCP — tell the user to use the TestDino UI. IMPORTANT: updates.tags must be a JSON array of strings — e.g. ["exploratory","auth"] — NOT a comma-separated string.

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": {
      "projectId": "<projectId>",
      "sessionId": "<sessionId>",
      "updates": "<updates>"
    },
    "name": "update_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
updatesYesFields to update: name, mission, sessionType, config, environment, releaseId, assigneeUserId, state, estimate, tags, linkedIssues. status="closed" closes the session.
projectIdYesProject ID
sessionIdYesInternal _id or counter-style ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.3
    • changedInput schema / properties / updates / description
      Previous value: -"Fields to update: name, mission, sessionType, config, environment, releaseId, assigneeUserId, state, estimate, tags, linkedIssues, attachments. status=\"closed\" closes the session."New value: +"Fields to update: name, mission, sessionType, config, environment, releaseId, assigneeUserId, state, estimate, tags, linkedIssues. status=\"closed\" closes the session."
  2. Changed6 schema fields changedv2.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / projectId / description
      Previous value: -"Project ID (required)."New value: +"Project ID"
    • changedInput schema / properties / sessionId / description
      Previous value: -"Internal _id or counter-style ID (required)."New value: +"Internal _id or counter-style ID"
    • addedInput schema / properties / updates / additionalProperties
      Added value: +{}
    • changedInput schema / properties / updates / description
      Previous value: -"Fields to update: name, mission, sessionType, config, environment, releaseId, assigneeUserId, state, estimate, tags, linkedIssues, attachments."New value: +"Fields to update: name, mission, sessionType, config, environment, releaseId, assigneeUserId, state, estimate, tags, linkedIssues, attachments. status=\"closed\" closes the session."
  3. Addedv1.0.10

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only flag destructiveHint=true; the description explains exactly what destruction means here — closing is permanent, freezes the session, snaps state to the project's "Done" option, and MCP cannot reopen it. It also adds a write-permission prerequisite and a partial-update contract ("send only fields you want to change") that no structured field conveys.

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?

Front-loaded with purpose then the irreversible-action warning, followed by permissions, allowed fields, and format gotchas in descending priority. The allowed-fields enumeration partially restates the schema's updates description, which is the only measurable waste in an otherwise dense block.

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 nested-object mutation tool with no output schema and a permissive additionalProperties schema, this covers the critical gaps: permanence of closing, permission requirement, partial-update semantics, and the tags encoding trap. It stops short of enumerating allowed values for fields like state or sessionType, which the loose schema also leaves undocumented, so a gap remains for an agent setting those.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds genuine meaning beyond it: the updates object is a sparse patch, and updates.tags must be a JSON array of strings, not a comma-separated string. That type constraint is not expressed anywhere in the schema, whose updates sub-object only allows arbitrary additional properties.

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?

Opens with a specific verb+resource pair: "Modify an existing exploratory session, or close it." The agent can immediately distinguish this from create_session and get_session without opening any schema.

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 explicit when/when-not guidance for the riskiest path: send updates.status="closed" only when the user asks to close, never as part of another edit. It also routes the out-of-scope case (adding files) to the TestDino UI rather than leaving the agent to guess.

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