argo-mcp

Update session

update_session

Idempotent

Reschedule a campaign session or edit its title/description. All fields optional. Owner-only on the backend.

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

Input Schema

Name	Required	Description
`endAt`	No	ISO-8601 instant.
`title`	No
`startAt`	No	ISO-8601 instant.
`sessionId`	Yes	Session ID.
`campaignId`	Yes	Campaign ID.
`description`	No

Output Schema

Name	Required	Description	Default
`id`	Yes
`endAt`	No
`title`	Yes
`guildId`	No
`startAt`	Yes
`createdAt`	No
`updatedAt`	No
`campaignId`	Yes
`description`	No
`invitedUserIds`	No
`createdByUserId`	No
`invitedPartyIds`	No
`attendanceReplies`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the annotations, the description adds important behavioral context: 'All fields optional' indicates partial update semantics, and 'Owner-only on the backend' discloses an authorization requirement. It does not contradict any annotations, and provides useful constraints not captured in the structured data.

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?

The description is a single, compact sentence that front-loads the primary action and includes essential constraints. Every word contributes value, with no redundancy or irrelevant detail.

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 simple update tool with an output schema and annotations covering safety, the description covers the core purpose, usage constraints, and key behaviors. It is complete enough for an agent to select and invoke the tool correctly, though it could add explicit guidance on when not to use it.

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?

The description groups startAt/endAt under 'reschedule' and title/description under 'edit', adding semantic meaning beyond the schema's bare parameter descriptions. With 67% schema coverage, the description helps clarify the purpose of these parameters, going beyond what the schema alone provides.

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?

The description clearly states the tool's function: rescheduling a session or editing its title/description. This distinguishes it from sibling tools like create_session, get_session, and list_sessions by specifying the update action and the specific fields it affects.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool (updating an existing session) and notes that all fields are optional, implying partial updates. However, it does not explicitly mention when not to use it or name alternatives like create_session for new sessions.

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

All argo-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.