Skip to main content
Glama

cc_status

View your current location, party summary, rare observations, and recent event log.

Instructions

View your current location, party summary, rare observations, and recent event log.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'cc_status' tool on the MCP server. It has no input schema and delegates to renderStatus().
    server.tool(
      'cc_status',
      'View your current location, party summary, rare observations, and recent event log.',
      {},
      async () => ok(renderStatus(requireGame())),
    );
  • The actual handler function `renderStatus` that builds the status overview string: location, party summary, rare observations, inventory, and recent event log.
    export function renderStatus(state: PlayerState): string {
      const area = AREAS[state.currentArea];
      const lines: string[] = [];
    
      lines.push(`${state.name.toUpperCase()}'S JOURNEY`);
      lines.push(`Location : ${area.name}`);
      const retiredLine = state.retired.length > 0 ? `  (${state.retired.length} at home)` : '';
      lines.push(`Party    : ${state.party.length}/4${retiredLine}`);
      lines.push(`Rares    : ${caughtRareCount(state)}/${RARE_SPECIES_IDS.length} caught  (${state.observedRares.length} sighted)`);
      lines.push(`Items    : ${state.inventory.length} carried`);
      lines.push('');
    
      // Inventory detail
      if (state.inventory.length > 0) {
        lines.push('CARRYING:');
        for (const id of state.inventory) {
          const item = ITEMS[id];
          if (!item) continue;
          lines.push(`  ${item.name}  —  ${item.effectLabel}`);
          lines.push(`    ${item.description}`);
        }
        lines.push('');
      }
    
      lines.push('RARE CREATURES:');
      for (const id of RARE_SPECIES_IDS) {
        const found   = state.observedRares.includes(id);
        const inParty = state.party.some(m => m.speciesId === id);
        const atHome  = state.retired.some(m => m.speciesId === id);
        let status = 'not yet found';
        if (inParty)      status = 'in party  ★';
        else if (atHome)  status = 'at home   ♥';
        else if (found)   status = 'observed  ✓';
        lines.push(`  ${SPECIES[id].name.padEnd(12)}  ${status}`);
      }
      lines.push('');
    
      // All-rares-caught nudge — fires only when each rare is actually in your care
      if (caughtRareCount(state) >= RARE_SPECIES_IDS.length && state.gameStatus !== 'won') {
        lines.push('');
        lines.push('✦ ─────────────────────────────────────── ✦');
        lines.push("  Old Maren's voice, somewhere in the back of your mind:");
        lines.push('  "You have all three. Bring them home."');
        lines.push('  Return to Millhaven to complete your journey.');
        lines.push('✦ ─────────────────────────────────────── ✦');
      }
    
      lines.push('');
      lines.push('RECENT LOG:');
      for (const entry of state.log) {
        lines.push(`  • ${entry}`);
      }
    
      return lines.join('\n');
    }
  • Helper function `caughtRareCount` used by renderStatus to count how many rare species the player currently has in their care.
    function caughtRareCount(state: PlayerState): number {
      return RARE_SPECIES_IDS.filter(id => ownsSpecies(state, id)).length;
    }
Behavior3/5

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

The description indicates a read-only operation ('View'), but no annotations are provided to confirm. It does not mention any side effects, state changes, or required permissions. The behavioral scope is implied but not explicitly disclosed, which is adequate given no parameters.

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 that directly lists the information the tool provides. It is concise with no unnecessary words, making it efficient for an agent to parse.

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 no output schema and zero parameters, the description adequately lists the tool's outputs. However, it lacks context about how this tool fits into the overall workflow or when it should be used compared to similar status tools like 'cc_party' or 'bs_get_state'.

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

Parameters5/5

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

The input schema has zero parameters, and the description adds no parameter-related information. Since schema coverage is 100%, the description cannot add value beyond the schema. A score of 5 is appropriate because there is no need for parameter documentation.

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 function: viewing current location, party summary, rare observations, and event log. It uses specific nouns and a verb ('View'), making the purpose clear. However, it does not differentiate from sibling tools like 'cc_party', which might also show party summary.

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?

No guidance is provided on when to use this tool versus alternatives such as 'cc_party' or 'bs_get_state'. There is no mention of prerequisites, context, or exclusions, leaving the agent without direction on appropriate usage.

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