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

worldanvil-mcp-server

by daireb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Who am I

get_identity

Verify World Anvil credentials by retrieving the authenticated user's ID and username. Confirm your connection is working.

Instructions

Return the authenticated World Anvil user (id + username). Use to verify credentials are working.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_identity"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It adds context by mentioning 'authenticated' and 'verify credentials', implying auth-dependency, but it does not explain behavior on invalid credentials or other failure modes. For a simple read operation this is acceptable but not rich.

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 short sentences, front-loaded with the core purpose and followed by a direct usage hint. Every word adds value; there is no fluff or redundancy.

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 parameterless tool with no output schema, the description sufficiently covers what the tool returns (id + username) and its intended use case (credential verification). Given the tool's simplicity, this is complete.

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 tool has zero parameters, so the baseline is 4. The description adds no parameter information because none are needed. It does clarify the return value (id + username), which is arguably more relevant for a parameterless tool.

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 returns the authenticated user's id and username, using a specific verb ('Return') and resource ('authenticated World Anvil user'). This distinguishes it from sibling tools that operate on worlds, articles, or assets.

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 explicitly says 'Use to verify credentials are working', providing a clear when-to-use context. It doesn't mention exclusions or alternatives, but given the tool's unique identity-checking purpose, no alternatives are needed.

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