Skip to main content
Glama
geneontology

Noctua MCP Server

Official
by geneontology

configure_token

Set the Barista authentication token to enable API access for Gene Ontology Causal Activity Model operations.

Instructions

Configure the Barista authentication token.

Args: token: The Barista authentication token

Returns: Success status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main implementation of the configure_token tool. It is decorated with @mcp.tool(), takes a token parameter, sets the BARISTA_TOKEN environment variable, resets the global _client to None (so the next call to get_client() creates a new BaristaClient with the new token), and returns a success response.
    @mcp.tool()
    async def configure_token(token: str) -> Dict[str, Any]:
        """
        Configure the Barista authentication token.
    
        Args:
            token: The Barista authentication token
    
        Returns:
            Success status
        """
        import os
        global _client
    
        # Set environment variable
        os.environ["BARISTA_TOKEN"] = token
    
        # Reset client to pick up new token
        _client = None
    
        return {
            "success": True,
            "configured": True
        }
  • The tool is registered via the @mcp.tool() decorator on line 64 of mcp_server.py. FastMCP automatically registers the function as an MCP tool named 'configure_token'.
    @mcp.tool()
  • The get_client() helper is used by other tools to obtain a BaristaClient. The _client global variable is reset to None by configure_token, forcing get_client() to create a new client with the updated token.
    def get_client() -> BaristaClient:
        """Get or create the Barista client instance."""
        global _client
        if _client is None:
            _client = BaristaClient()
        return _client
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses minimal behavioral information (configuring a token, returning success status) but does not mention side effects, persistence, or idempotency.

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 concise, with only necessary lines describing purpose, argument, and return. It is front-loaded with the purpose and uses a clear Args/Returns structure with no wasted words.

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 simplicity (one parameter, output schema exists), the description is mostly complete. It mentions the return value, but could optionally note whether the token is persisted or used in subsequent requests.

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?

Schema description coverage is 0%. The description adds meaning by specifying that the token is a 'Barista authentication token,' which goes beyond the type 'string' and clarifies its purpose.

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 configures the Barista authentication token, which is a specific verb+resource. It distinguishes itself from sibling tools that are primarily about data manipulation, search, or model management.

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, such as prerequisites or usage context. It only states the argument and return value.

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