Skip to main content
Glama

cc_party

Check your party's bond levels, moods, personalities, and discovered traits.

Instructions

View your full party — bond levels, moods, personalities, and any discovered traits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool 'cc_party' is registered via server.tool() with an empty schema (no params). The handler calls renderParty(requireGame()) which renders the full party detail view.
    server.tool(
      'cc_party',
      'View your full party — bond levels, moods, personalities, and any discovered traits.',
      {},
      async () => ok(renderParty(requireGame())),
    );
  • The renderParty() function is the actual handler logic for cc_party. It builds a detailed view of the player's party including bond levels, moods, personalities, species names, secret traits for rare creatures, and retired creatures at home in Millhaven.
    // ── Party detail view (cc_party) ───────────────────────────────────────────
    
    export function renderParty(state: PlayerState): string {
      const lines: string[] = [];
    
      if (state.party.length === 0 && state.retired.length === 0) {
        return 'Your party is empty. Head into the meadow or forest to find creatures.';
      }
    
      if (state.party.length > 0) {
        lines.push(`YOUR PARTY  (${state.party.length}/4)`);
        lines.push('(Bond grows through time together. Watch for shifts in mood as trust deepens.)');
        lines.push('');
    
        for (const m of state.party) {
          const species = SPECIES[m.speciesId];
          const header  = m.isRare ? `★ ${m.nickname.toUpperCase()}` : m.nickname.toUpperCase();
          const subname = m.nickname !== species.name ? `  ${species.name}` : '';
    
          lines.push(`${header}${subname}`);
          lines.push(`  "${species.personalityNote}"`);
          lines.push(`  Bond  ${bondBar(m.bondLevel)}`);
          lines.push(`  Mood  ${m.mood}  ${moodIcon(m.mood)}`);
          lines.push(`  ${species.bondQuotes[bondTier(m.bondLevel)]}`);
          lines.push(`  Caught at: ${m.caughtAt}`);
    
          if (species.secretTrait && m.isRare) {
            lines.push(`  ✦ ${species.secretTrait}`);
          }
          lines.push('');
        }
      } else {
        lines.push('YOUR PARTY  (empty)');
        lines.push('');
      }
    
      if (state.retired.length > 0) {
        lines.push('AT HOME IN MILLHAVEN:');
        lines.push('(Safe, warm, and waiting for your return.)');
        lines.push('');
    
        for (const m of state.retired) {
          const species = SPECIES[m.speciesId];
          const header  = m.isRare ? `★ ${m.nickname.toUpperCase()}` : m.nickname.toUpperCase();
          const subname = m.nickname !== species.name ? `  ${species.name}` : '';
    
          lines.push(`${header}${subname}`);
          lines.push(`  Bond  ${bondBar(m.bondLevel)}`);
          lines.push(`  ${species.bondQuotes.high}`);
          lines.push('');
        }
      }
    
      return lines.join('\n');
    }
  • The registerCritterCatchTools() function is the export that registers all Critter Catch tools including cc_party on the McpServer instance.
    export function registerCritterCatchTools(server: McpServer): void {
  • The renderParty function is imported from './render.js' and used by the cc_party tool handler.
    import { renderArea, renderExploreUpdate, renderParty, renderStatus, renderWin } from './render.js';
Behavior4/5

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

Without annotations, the description transparently states the tool is for viewing (read-only) and enumerates the returned information (bond levels, moods, etc.). It does not mention prerequisites or side effects, but for a simple view tool, this is sufficient.

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 a single sentence of 10 words, perfectly concise and front-loaded with the core purpose. No extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters and no output schema, the description adequately covers the tool's output categories. It could specify if the party includes all characters or only active ones, but for a brief tool, it is complete enough.

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 input schema has zero parameters, so parameter semantics are not needed. Baseline is 4, and the description does not add parameter info, which is appropriate.

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 'View your full party' which is a specific verb+resource. It lists the details returned (bond levels, moods, personalities, traits), distinguishing it from other cc_ tools like cc_catch or cc_explore which involve actions.

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?

The description implies usage when wanting to check party info, but it lacks explicit when-not or alternative guidance. Siblings such as cc_status or cc_recall might overlap, but no differentiation is 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/SrmTech-git/MCPArcade'

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