Skip to main content
Glama
geneontology

Noctua MCP Server

Official
by geneontology

search_models

Search GO-CAM biological models by title, state, contributor, group, publication, or gene product to find relevant models with metadata.

Instructions

Search for GO-CAM models based on various criteria.

Allows searching models by title, state, contributor, group, publication, or gene product. Returns a list of matching models with their metadata.

Args: title: Search for models containing this text in their title state: Filter by model state (production, development, internal_test) contributor: Filter by contributor ORCID (e.g., 'https://orcid.org/0000-0002-6601-2165') group: Filter by group/provider (e.g., 'http://www.wormbase.org') pmid: Filter by PubMed ID (e.g., 'PMID:12345678') gene_product: Filter by gene product (e.g., 'UniProtKB:Q9BRQ8', 'MGI:MGI:97490') limit: Maximum number of results to return (default: 50) offset: Offset for pagination (default: 0)

Returns: Dictionary containing search results with model metadata

Examples: # Search for all production models results = search_models(state="production")

# Find models containing "Wnt signaling" in title
results = search_models(title="Wnt signaling")

# Find models for a specific gene product
results = search_models(gene_product="UniProtKB:P38398")

# Find models from a specific paper
results = search_models(pmid="PMID:30194302")

# Find models by a specific contributor
results = search_models(
    contributor="https://orcid.org/0000-0002-6601-2165"
)

# Combine filters
results = search_models(
    state="production",
    title="kinase",
    limit=10
)

# Pagination example
page1 = search_models(limit=50, offset=0)
page2 = search_models(limit=50, offset=50)

# Find models from specific research group
results = search_models(group="http://www.wormbase.org")

# Search for development models with specific gene
results = search_models(
    state="development",
    gene_product="MGI:MGI:97490"
)

Notes: - Results include model ID, title, state, contributors, and dates - Use pagination (offset/limit) for large result sets - Filters can be combined for more specific searches - Gene products can be from various databases (UniProt, MGI, RGD, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
stateNo
contributorNo
groupNo
pmidNo
gene_productNo
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler implementation for the 'search_models' tool. This async function is decorated with @mcp.tool(), which both defines the input schema via type hints/docstring and registers/executes the tool logic. It uses BaristaClient.list_models to perform the search with optional filters and handles exceptions.
    @mcp.tool()
    async def search_models(
        title: Optional[str] = None,
        state: Optional[str] = None,
        contributor: Optional[str] = None,
        group: Optional[str] = None,
        pmid: Optional[str] = None,
        gene_product: Optional[str] = None,
        limit: int = 50,
        offset: int = 0
    ) -> Dict[str, Any]:
        """
        Search for GO-CAM models based on various criteria.
    
        Allows searching models by title, state, contributor, group, publication, or gene product.
        Returns a list of matching models with their metadata.
    
        Args:
            title: Search for models containing this text in their title
            state: Filter by model state (production, development, internal_test)
            contributor: Filter by contributor ORCID (e.g., 'https://orcid.org/0000-0002-6601-2165')
            group: Filter by group/provider (e.g., 'http://www.wormbase.org')
            pmid: Filter by PubMed ID (e.g., 'PMID:12345678')
            gene_product: Filter by gene product (e.g., 'UniProtKB:Q9BRQ8', 'MGI:MGI:97490')
            limit: Maximum number of results to return (default: 50)
            offset: Offset for pagination (default: 0)
    
        Returns:
            Dictionary containing search results with model metadata
    
        Examples:
            # Search for all production models
            results = search_models(state="production")
    
            # Find models containing "Wnt signaling" in title
            results = search_models(title="Wnt signaling")
    
            # Find models for a specific gene product
            results = search_models(gene_product="UniProtKB:P38398")
    
            # Find models from a specific paper
            results = search_models(pmid="PMID:30194302")
    
            # Find models by a specific contributor
            results = search_models(
                contributor="https://orcid.org/0000-0002-6601-2165"
            )
    
            # Combine filters
            results = search_models(
                state="production",
                title="kinase",
                limit=10
            )
    
            # Pagination example
            page1 = search_models(limit=50, offset=0)
            page2 = search_models(limit=50, offset=50)
    
            # Find models from specific research group
            results = search_models(group="http://www.wormbase.org")
    
            # Search for development models with specific gene
            results = search_models(
                state="development",
                gene_product="MGI:MGI:97490"
            )
    
        Notes:
            - Results include model ID, title, state, contributors, and dates
            - Use pagination (offset/limit) for large result sets
            - Filters can be combined for more specific searches
            - Gene products can be from various databases (UniProt, MGI, RGD, etc.)
        """
        client = get_client()
    
        try:
            results = client.list_models(
                title=title,
                state=state,
                contributor=contributor,
                group=group,
                pmid=pmid,
                gp=gene_product,
                limit=limit,
                offset=offset
            )
            return results
        except Exception as e:
            return {
                "error": "Failed to search models",
                "message": str(e)
            }
Behavior4/5

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

With no annotations provided, the description carries full burden and does well. It discloses key behavioral traits: the tool returns a list of matching models with metadata, includes pagination guidance ('Use pagination for large result sets'), notes that filters can be combined, and describes result content ('model ID, title, state, contributors, and dates'). It doesn't mention rate limits or authentication needs, but covers core behavior adequately.

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 description is well-structured with clear sections (description, args, returns, examples, notes) and front-loaded core purpose. However, it includes 10 detailed examples, which may be excessive—some could be condensed without losing value. Every sentence earns its place, but the length pushes it slightly below perfect conciseness.

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

Completeness5/5

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

Given the tool's complexity (8 parameters, search functionality) and lack of annotations, the description is highly complete. It explains purpose, parameters, usage, examples, and behavioral notes. With an output schema present, it doesn't need to detail return values, and it fully compensates for 0% schema coverage. No gaps remain for effective agent use.

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?

Schema description coverage is 0%, so the description must compensate fully. It provides detailed semantics for all 8 parameters: each has a clear explanation (e.g., 'title: Search for models containing this text in their title'), examples of valid values (e.g., 'PMID:12345678'), and default values for 'limit' and 'offset'. This adds substantial meaning beyond the bare schema.

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 the tool's purpose: 'Search for GO-CAM models based on various criteria.' It specifies the verb ('Search'), resource ('GO-CAM models'), and scope ('based on various criteria'), distinguishing it from siblings like 'get_model' (singular retrieval) and 'search_annotations'/'search_bioentities' (different resource types).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool: for searching models with various filters. It implies usage through examples like 'Search for all production models' or 'Find models containing "Wnt signaling" in title.' However, it doesn't explicitly state when NOT to use it or name alternatives (e.g., 'get_model' for single-model retrieval), missing full sibling differentiation.

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/geneontology/noctua-mcp'

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