argo-mcp

Set quest objective state

set_quest_objective_state

Idempotent

Tick, fail or reopen one objective of a quest by its id (get_mnemon's quest.objectives[].id), at any depth, without rewriting the quest. A GM sets any state. A player may only tick an objective they can see done, or undo that, and only while the quest's playersCanTick is on. Returns the quest as get_mnemon shows it, its progress recounted.

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>",
      "entryId": "<entryId>",
      "objectiveId": "<objectiveId>",
      "state": "<state>"
    },
    "name": "set_quest_objective_state"
  }
}

Input Schema

Name	Required	Description
`state`	Yes	open, done or failed.
`entryId`	Yes	The quest: entryId (hex) or exact title.
`campaignId`	Yes	Campaign ID.
`objectiveId`	Yes	The objective, as get_mnemon's quest.objectives[].id names it.

Output Schema

Name	Required	Description
`type`	Yes
`quest`	No	Quests only: status, kind, objectives, reward chips and progress as this user may see them.
`title`	Yes
`blocks`	Yes
`entryId`	Yes
`typeProperties`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 29, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only supply readOnly=false, idempotent=true, destructive=false; the description adds substantial behavioral context beyond them: the full role/permission model, the playersCanTick gate, and the return contract (quest as get_mnemon shows it, progress recounted). These are exactly the traits an agent needs to invoke safely.

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?

Three tight sentences, front-loaded with the core action and reference resolution, then permissions, then return value. Dense but every sentence carries weight; minor stutter in the reference detail keeps it from a 5.

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

Completeness5/5

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

Despite an output schema existing, the description still frames the return shape relative to get_mnemon, and it fully covers the permission model, target addressing, and the fact that the quest is not rewritten. Nothing an agent needs to call it correctly is missing.

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 campaignId, entryId, objectiveId, and the state enum. The description adds 'at any depth' for objectiveId and confirms the state triad, but largely restates schema content; baseline 3 is appropriate.

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?

States a precise verb set (tick/fail/reopen) on a specific resource (one objective of a quest by id) and scopes it to any depth without rewriting the quest. This clearly separates it from sibling writers like update_quest_mnemon, so an agent can route correctly without opening schemas.

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?

Gives explicit conditional usage: a GM sets any state, a player may only tick a visibly-done objective (or undo that) and only while playersCanTick is on. It implies the alternative (in-place edit vs rewriting the quest) but never names a sibling tool directly, so it falls just short of a 5.

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.