Skip to main content
Glama

cc_release

Permanently remove a creature from your party by specifying its nickname or species name.

Instructions

Release a creature from your party. This cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nicknameYesThe nickname (or species name) of the creature to release.

Implementation Reference

  • The main handler function for the cc_release tool. It finds a party member by nickname (case-insensitive), permanently removes them from the party, renders a bond-tier farewell quote, then calls maybeAcceptPending to auto-join any pending catch if a slot opened.
    server.tool(
      'cc_release',
      'Release a creature from your party. This cannot be undone.',
      { nickname: z.string().describe("The nickname (or species name) of the creature to release.") },
      async ({ nickname }) => {
        const s   = requireGame();
        const turnBlock = checkTurn(s); if (turnBlock) return turnBlock;
        const idx = s.party.findIndex(m => m.nickname.toLowerCase() === nickname.toLowerCase());
    
        if (idx === -1) {
          const names = s.party.map(m => m.nickname).join(', ') || 'empty';
          return err(`No creature named "${nickname}" in your party.\n\nParty: ${names}`);
        }
    
        const member  = s.party[idx];
        const species = SPECIES[member.speciesId];
        s.party.splice(idx, 1);
        addToLog(s, `Released ${member.nickname}.`);
    
        const lines = [
          `${member.nickname} ${species.bondQuotes[bondTier(member.bondLevel)]}.`,
          'Then it turns and goes.',
        ];
    
        maybeAcceptPending(s, lines);
    
        lines.push('', renderParty(s));
        return ok(lines.join('\n'));
      },
  • The Zod schema for cc_release's input: a required string field 'nickname' described as 'The nickname (or species name) of the creature to release.'
    { nickname: z.string().describe("The nickname (or species name) of the creature to release.") },
  • Registration of the cc_release tool via server.tool() inside the registerCritterCatchTools function. The tool is named 'cc_release' with description 'Release a creature from your party. This cannot be undone.'
    server.tool(
      'cc_release',
  • Helper function maybeAcceptPending called by cc_release. If a creature is pending (party was full during catch), releasing a creature opens a slot and this function auto-joins the pending creature into the party.
    function maybeAcceptPending(s: PlayerState, lines: string[]): void {
      if (!s.pendingCatch) return;
      const incoming        = s.pendingCatch;
      const incomingSpecies = SPECIES[incoming.speciesId];
      s.party.push(incoming);
      s.pendingCatch = null;
      addToLog(s, `${incoming.nickname} joined the party.`);
      lines.push(
        '',
        `${incoming.nickname} steps forward to take their place.`,
        '',
        incomingSpecies.description,
        `"${incomingSpecies.personalityNote}"`,
      );
      if (incomingSpecies.secretTrait) {
        lines.push('', `✦ ${incomingSpecies.secretTrait}`);
      }
    }
Behavior2/5

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

No annotations are present, so the description bears full responsibility. It only mentions irreversibility and omits other behavioral details such as prerequisites, effects on game state, or whether the creature is lost permanently. Minimal transparency.

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?

Two short sentences: first states purpose, second adds a critical warning. No wasted words, front-loaded with key 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?

For a simple tool with one parameter and no output schema, the description provides sufficient information about the action and its irreversibility. It could be enhanced by clarifying the relationship to sibling tools, but overall it is complete enough.

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

Parameters3/5

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

Schema coverage is 100%, so the description of the 'nickname' parameter adds no new meaning beyond what is already in the schema. Baseline score applies.

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 action (release) and the resource (creature from party). However, it does not differentiate from sibling tools like cc_recall or cc_retire, which may also modify party membership.

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 includes a warning that the action cannot be undone, which implies caution, but it lacks explicit guidance on when to use this tool versus alternatives like cc_recall or cc_retire.

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