Skip to main content
Glama
Sign In
worldanvil-mcp-server

worldanvil-mcp-server

by daireb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get world details

get_world

Retrieve complete details of a specific world, including description, settings, counts, and links, using its world_id obtained from list_worlds.

Instructions

Full details of one world: description, settings, counts and links. Use list_worlds first to find the world_id.

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": {
      "world_id": "<world_id>"
    },
    "name": "get_world"
  }
}

Input Schema

NameRequiredDescriptionDefault
world_idYesUUID of the world

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It states exactly what the tool returns (description, settings, counts, links). While it does not explicitly say it's read-only or mention error behavior, the 'get' verb and content list make the behavior reasonably transparent.

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 two sentences with no fluff. The first sentence front-loads the purpose and return contents; the second provides a concise, useful prerequisite. Every word earns its place.

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 simple one-parameter getter without an output schema, the description fully covers what the tool does, what it returns, and how to use it. No critical information is missing for an agent to select and invoke the tool correctly.

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 schema fully describes world_id as a UUID, so baseline is 3. The description adds value by explaining how to obtain the world_id (via list_worlds), enriching the parameter semantics beyond the schema.

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 identifies the tool as retrieving full details for a single world, listing specific content categories (description, settings, counts, links). It distinguishes from list_worlds by focusing on a single world, and from other siblings by its resource specificity.

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?

The description explicitly instructs to use list_worlds first to obtain the required world_id, providing clear sequencing and an alternative when the ID is unknown. This is direct, actionable guidance for when to use this tool.

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