Skip to main content
Glama
biocontext-ai

protocol-mcp

by biocontext-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{
  "tasks": {
    "list": {},
    "cancel": {},
    "requests": {
      "tools": {
        "call": {}
      },
      "prompts": {
        "get": {}
      },
      "resources": {
        "read": {}
      }
    }
  }
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_protocolsA

Search protocols.io for laboratory protocols.

Parameters

query : str Search term to find protocols. max_results : int Number of results (1-50), defaults to 10.

Returns

str Formatted list of matching protocols with title, DOI, URI, and step count.

get_protocolA

Retrieve full protocol details from protocols.io.

Parameters

protocol_id : str Protocol identifier - can be a URI (e.g., 'rna-extraction-abc123'), DOI (e.g., '10.17504/protocols.io.xxx'), or numeric ID. include_steps : bool Whether to include step-by-step instructions, defaults to True. include_materials : bool Whether to include materials/reagents list, defaults to True.

Returns

str Formatted markdown with protocol metadata, materials, and steps.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one retrieves a specific protocol by ID, the other searches for protocols by query. No overlap in functionality.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with underscores: 'get_protocol' and 'search_protocols'. The naming is predictable and clear.

Tool Count2/5

With only 2 tools, the server feels under-scoped for the domain of laboratory protocols. A typical server covering protocols would require more tools for CRUD operations and listing.

Completeness2/5

The server only provides read operations (get and search). Missing create, update, delete, and list functionalities, leaving significant gaps in protocol management.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources