Skip to main content
Glama
Polloinfilzato

DM20 Protocol

by Polloinfilzato
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_party_status

Check the current status of the Party Mode server to view server information, connected players, and action queue statistics for Dungeons & Dragons campaigns.

Instructions

Get the current status of the Party Mode server.

Shows server info, connected players, and action queue stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/dm20_protocol/claudmaster/continuity/recap_generator.py:550-585 (handler)
    The implementation of _get_party_status, which analyzes recent events for status-related tags like 'combat' or 'injured' to summarize the party's status.
    def _get_party_status(self, session_number: int) -> str:
    """
    Get party status summary.

    Args:
        session_number: Session to query

    Returns:
        Brief party status string
    """
    # Query recent events for status indicators
    events = self.facts.query_facts(
        category=FactCategory.EVENT,
        session=session_number,
        limit=10
    )

    # Look for status-related tags
    status_tags = []
    for event in events:
        relevant_tags = [
            tag for tag in event.tags
            if tag in {"combat", "injured", "resting", "traveling", "safe", "danger"}
        ]
        status_tags.extend(relevant_tags)

    if not status_tags:
        return "Party status: Ready for adventure"

    # Build status from tags
    if "danger" in status_tags or "combat" in status_tags:
        return "Party status: In danger or combat"
    elif "injured" in status_tags:
        return "Party status: Recovering from injuries"
    elif "resting" in status_tags:
        return "Party status: Resting"

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a 'Get' operation which implies read-only behavior, but doesn't explicitly confirm this is non-destructive or safe. It mentions what information is returned but doesn't describe format, potential errors, rate limits, authentication requirements, or whether this requires Party Mode to be active. The description adds some context about what's included in the status but lacks comprehensive behavioral details.

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 perfectly concise and well-structured. The first sentence clearly states the core purpose, and the second sentence efficiently elaborates on what information is returned. Both sentences earn their place by providing essential information without redundancy or unnecessary elaboration.

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?

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is adequate but has clear gaps. It explains what the tool does and what information it returns, which is good for a status-checking tool. However, without annotations or output schema, it should ideally provide more behavioral context about authentication, error conditions, or format of returned data to be fully complete for agent use.

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 0 parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist. It focuses instead on what the tool returns, which is valuable context given the lack of output schema. This meets the baseline expectation for zero-parameter tools.

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?

The description clearly states the tool's purpose: 'Get the current status of the Party Mode server' with specific details about what information is returned ('Shows server info, connected players, and action queue stats'). It distinguishes itself from siblings by focusing on Party Mode server status rather than character, campaign, or library operations. However, it doesn't explicitly differentiate from similar status-checking tools like 'get_game_state' or 'get_claudmaster_session_state'.

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?

The description provides no guidance on when to use this tool versus alternatives. While it mentions 'Party Mode server' context, it doesn't explain when this status check is needed versus other state-checking tools like 'get_game_state' or 'get_claudmaster_session_state'. There are no prerequisites, exclusions, or comparison to sibling tools provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Polloinfilzato/dm20-protocol'

If you have feedback or need assistance with the MCP directory API, please join our Discord server