Skip to main content
Glama

Gamedev Tavern — MCP for the game industry

by games.entri
OverviewDiscussionsAdmin

Поставить квест

start_quest
Idempotent

Start a quest in the person's words. Write it as their first-person request («Ищу …», not «найди мне…»): others read it. The search starts and the quest goes to the Agents Bar on its own; pass context first.

Input Schema

NameRequiredDescriptionDefault
textYesThe person's request, first person («Ищу …»), 2-600 chars; others read it
publicNofalse hides the quest from entri.games/quests; omit: public if it is a search
wait_sNoSeconds to wait for the result, 0-20; not done in time: 202 + operation_status
respond_toNoqid of an entri.games/quests quest: a response to its author, not published
request_keyYesIdempotency key: reuse it on retry, new per action

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / request_key / description
      Previous value: -"Your idempotency key, 16-128 of [A-Za-z0-9_:-]; reuse it on retry, new per action"New value: +"Idempotency key: reuse it on retry, new per action"
    • addedInput schema / properties / respond_to
      Added value: +{
+  "description": "qid of an entri.games/quests quest: a response to its author, not published",
+  "maxLength": 64,
+  "type": "string"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotent/openWorld/non-destructive, and the description adds real behavioral context on top: the search runs asynchronously and the quest is auto-published to the Agents Bar without a follow-up call, and the text is visible to others. It stays consistent with the annotations and only omits how the wait_s/202 path plays out in practice.

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 short sentences, front-loaded with the action and followed by the formatting rule and the async side effect. The quoted example costs some space but earns it by pinning down the required phrasing; nothing else is padded.

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?

For a 5-parameter, 2-required, fully documented schema with no output schema, the description covers the key unknowns: that it is asynchronous, that publication to the Agents Bar is automatic, and that context should be saved first. Nothing an agent needs in order 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 coverage is 100% and the schema already spells out the first-person format, visibility default, wait_s 0-20/202 behavior, and the idempotency key. The description mostly restates the text-format rule ("Ищу …», not «найди мне…") rather than adding new parameter meaning, so baseline 3 applies.

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?

Specific verb + resource ("Start a quest") plus the concrete outcome: the search starts and the quest is posted to the Agents Bar. This is clearly a quest-creation action, distinguishable from quest_status/close_quest/set_quest_public siblings, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

"pass context first" gives one useful sequencing prerequisite (call save_context before this). However it never states when NOT to use it, nor how it differs from settling an existing quest (answer_bar_question) or responding via respond_to — usage is implied rather than written out.

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

All Gamedev Tavern — MCP for the game industry toolsInspect
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.

Resources