Skip to main content
Glama
ellmos-codecommander-mcp

ellmos-codecommander-mcp

Scan Emoji

cc_scan_emoji
Read-onlyIdempotent

Scans files and directories for emojis and reports ASCII alternatives for systems that do not support Unicode or emoji.

Instructions

Scans files for emojis and shows ASCII alternatives.

Args:

  • path (string): Path to the file or directory

  • recursive (boolean): Scan recursively

  • extensions (string): Only certain extensions

Useful for systems that don't support Unicode/Emoji.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "cc_scan_emoji"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath
recursiveNoRecursive
extensionsNoExtensions.py,.js,.ts,.json,.md,.txt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.27
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.3.8

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds the useful detail that output consists of ASCII alternatives, but says nothing about the report shape (per-file? per-occurrence?) or limits on large recursive scans.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the motivating use case are front-loaded in a single sentence, and the whole definition is short. The inline Args block is redundant with a fully described schema, so a little space is wasted.

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?

For a simple three-parameter read-only scan, annotations and schema cover most needs, and the description supplies purpose plus motivation. What remains missing is any indication of the returned report's form, which matters given there is no output schema.

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 description coverage is 100%, so the schema already carries the parameter burden; the description's Args block largely restates it, though "Only certain extensions" adds a hint of filter semantics. No format example for the extensions string beyond what the default value shows in the schema.

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?

States a specific verb and resource: scans files for emojis and shows ASCII alternatives. The resource scope (files, optionally recursive with extension filters) is clear enough to distinguish it from unrelated siblings, though no sibling (e.g. cc_fix_umlauts, cc_fix_encoding) is named for contrast.

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?

"Useful for systems that don't support Unicode/Emoji" implies the motivating scenario but gives no explicit when-to-use/when-not rules, no mention of complementary tools like cc_fix_umlauts or cc_fix_encoding, and no note on whether this reports or rewrites.

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