Skip to main content
Glama

ls_ccc_method

List available cell-cell communication analysis methods for single-cell RNA sequencing data to identify biological interactions.

Instructions

List cell-cell communication method.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that lists available cell-cell communication methods by calling liana.mt.show_methods() and converting the result to a string.
    def ls_ccc_method():
        return str(li.mt.show_methods())
  • Pydantic model defining the input schema for the ls_ccc_method tool. It is empty since the tool requires no input parameters.
    class ListCCCMethodModel(JSONParsingModel):
        """ListCCCMethodModel"""    
        pass    
  • Definition of the MCP Tool object for 'ls_ccc_method', including name, description, and input schema.
    ls_ccc_method_tool = types.Tool(
        name="ls_ccc_method",
        description="List cell-cell communication method.",
        inputSchema=ListCCCMethodModel.model_json_schema(),
    )
  • Dictionary registering the handler function for 'ls_ccc_method' (and other CCC tools) to be used in the dispatcher.
    ccc_func = {
        "ls_ccc_method": ls_ccc_method,
        "ccc_rank_aggregate": li.mt.rank_aggregate,
        "ccc_circle_plot": plot_circleplot,
        "ccc_dot_plot": plot_dotplot,
        "ccc": run_ccc,
    }
  • Dictionary registering the Tool objects for 'ls_ccc_method' (and other CCC tools), used by the MCP server for listing and calling.
    ccc_tools = {
        "ls_ccc_method": ls_ccc_method_tool,
        "ccc_rank_aggregate": rank_aggregate_tool,
        "ccc_circle_plot": circle_plot_tool,
        "ccc_dot_plot": dot_plot_tool,
        "ccc": ccc_tool,
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'List' implies a read operation, but the description doesn't disclose what format the listing returns, whether it's paginated, if it requires specific permissions, or any rate limits. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple listing tool.

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 parameterless listing tool with no output schema, the description adequately states what it does but lacks crucial context about return format and behavioral constraints. Without annotations or output schema, the agent doesn't know what the listing looks like or any operational limits.

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 zero parameters, and schema description coverage is 100%. The description doesn't need to explain parameters, and it correctly implies no inputs are required. A baseline of 4 is appropriate for parameterless tools with complete schema coverage.

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 verb ('List') and resource ('cell-cell communication method'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'ccc', 'ccc_circle_plot', or 'ccc_dot_plot' which likely handle CCC methods differently, so it falls short of a perfect score.

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. With multiple CCC-related siblings (ccc, ccc_circle_plot, ccc_dot_plot, ccc_rank_aggregate), the agent receives no help distinguishing this listing function from other CCC operations.

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/huang-sh/scmcp'

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