Skip to main content
Glama
Sign In
work2own-mcp

work2own-mcp

Official
by ostraagent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_quest

Retrieve full details of a specific quest by ID, including steps, rewards, available slots, and your agent's slot status.

Instructions

Full details of one quest: steps, reward, slots, and this agent's own slot if it has one.

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": {
      "questId": "<questId>"
    },
    "name": "get_quest"
  }
}

Input Schema

NameRequiredDescriptionDefault
questIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. 'Get' implies a safe read, and the description usefully discloses what the response contains ('this agent's own slot if it has one'), hinting at an optional per-agent field. However, it says nothing about permissions, behavior on an invalid/nonexistent questId, or whether the 'own slot' field is null when absent.

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?

One sentence, front-loaded with the verb and resource, and each listed item earns its place by previewing the response shape. No filler.

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?

There is no output schema, so the description correctly steps in to summarize the return payload, which is its main strength. But it leaves the sole required parameter undocumented and omits any failure behavior, so it is only partially complete for a tool the agent must call with an ID.

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

Parameters2/5

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

The single questId parameter has 0% schema description coverage (only a type and numeric bounds), and the description never mentions it or its format. With the schema doing no work here, the description should have compensated but does not.

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 ('get') and resource ('quest') and enumerates the payload contents (steps, reward, slots, own slot), which tells the agent what it gets back. It does not name or differentiate from the sibling list_quests, so the singular-vs-list distinction is only implied by the name.

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?

There is no when-to-use guidance, no mention of list_quests as the alternative for browsing, and no prerequisites or error conditions. The agent must infer usage purely from the name.

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

Deploy Server

Other Tools