Skip to main content
Glama
geneontology

Noctua MCP Server

Official
by geneontology

get_guideline_content

Fetch a specific GO-CAM guideline by its name, providing detailed annotation rules and examples.

Instructions

Fetch specific GO-CAM guideline content.

Args: guideline_name: Name of guideline file (without .md extension). Use list_guidelines() to see available options.

Returns: Dictionary with guideline content or error message

Examples: # Get a specific guideline content = get_guideline_content("E3_ubiquitin_ligases")

# Get transcription factor guidelines
content = get_guideline_content("DNA-binding_transcription_factor_activity_annotation_guidelines")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guideline_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'get_guideline_content' tool handler function. Registered with @mcp.tool() decorator. Accepts a guideline_name parameter (filename without .md extension), reads the .md file from the GUIDELINES_DIR directory, and returns its content along with metadata like description and length. Returns an error if the file doesn't exist, listing available alternatives.
    @mcp.tool()
    async def get_guideline_content(guideline_name: str) -> Dict[str, Any]:
        """Fetch specific GO-CAM guideline content.
    
        Args:
            guideline_name: Name of guideline file (without .md extension).
                           Use list_guidelines() to see available options.
    
        Returns:
            Dictionary with guideline content or error message
    
        Examples:
            # Get a specific guideline
            content = get_guideline_content("E3_ubiquitin_ligases")
    
            # Get transcription factor guidelines
            content = get_guideline_content("DNA-binding_transcription_factor_activity_annotation_guidelines")
        """
        file_path = GUIDELINES_DIR / f"{guideline_name}.md"
    
        if not file_path.exists():
            available = _get_available_guidelines()
            return {
                "success": False,
                "error": f"Guideline '{guideline_name}' not found",
                "available_guidelines": available,
                "hint": "Use one of the available guideline names listed above"
            }
    
        try:
            with open(file_path) as f:
                content = f.read()
    
            # Extract first heading as description
            lines = content.split('\n')
            description = ""
            for line in lines:
                if line.strip():
                    description = line.strip('#').strip()
                    break
    
            return {
                "success": True,
                "guideline_name": guideline_name,
                "description": description,
                "content": content,
                "length": len(content)
            }
        except Exception as e:
            return {
                "success": False,
                "error": f"Failed to read guideline: {str(e)}",
                "guideline_name": guideline_name
            }
  • Registration of 'get_guideline_content' as an MCP tool via the @mcp.tool() decorator on line 1904.
    @mcp.tool()
    async def get_guideline_content(guideline_name: str) -> Dict[str, Any]:
  • Helper function _get_available_guidelines() that lists available guideline files in the GUIDELINES_DIR directory. Used by both list_guidelines() tool and get_guideline_content tool.
    def _get_available_guidelines() -> List[str]:
        """Get list of available guideline files."""
        if not GUIDELINES_DIR.exists():
            return []
        return sorted([f.stem for f in GUIDELINES_DIR.glob("*.md")])
  • Helper function _inject_guideline_list() which appends a list of available guidelines to markdown content and references the get_guideline_content tool.
    def _inject_guideline_list(content: str, title: str) -> str:
        """Inject list of available guidelines at the end of content."""
        guidelines = _get_available_guidelines()
        if not guidelines:
            return content
    
        # Create formatted list
        guideline_section = "\n\n## Available GO-CAM Guidelines\n\n"
        guideline_section += f"This is the '{title}' guideline. Other available guidelines include:\n\n"
    
        for guide in guidelines:
            # Skip the current one
            if guide == title:
                continue
            # Make the filename more readable
            readable_name = guide.replace("_", " ").replace("-", " ")
            guideline_section += f"- {readable_name}\n"
    
        guideline_section += "\nUse the `get_guideline_content` tool to access any specific guideline."
    
        return content + guideline_section
  • Definition of GUIDELINES_DIR at module level (Path(__file__).parent / 'guidelines'), used by get_guideline_content and related guideline tools.
    GUIDELINES_DIR = Path(__file__).parent / "guidelines"
Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. It mentions the return type (dictionary with content or error) but lacks details on side effects, authentication needs, or rate limits. The read-only nature is implicit but not explicit.

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 Args, Returns, and Examples sections. It is front-loaded with the purpose. While each sentence adds value, the examples could be slightly more concise without loss of clarity.

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?

Given the tool's low complexity (one string parameter) and the existence of an output schema, the description provides sufficient context. It references the sibling list_guidelines and describes the return type. No major gaps are present.

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 schema has 0% description coverage, but the description adds substantial meaning: the parameter is a filename without extension and suggests using list_guidelines() for options. This goes beyond the schema's bare type information.

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 explicitly states 'Fetch specific GO-CAM guideline content,' providing a clear verb and resource. It distinguishes itself from the sibling tool 'list_guidelines' by focusing on content retrieval given a name.

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 advises using list_guidelines() to see available options, offering clear prerequisite guidance. However, it does not explicitly state when not to use this tool or discuss alternatives beyond the sister tool.

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