Glow Research Docs

Read and compare lab documents

Find reviewed Glow public research documentation, read a cited example laboratory report, and compare a lot label with the report’s lot identifier. The app explains testing scope and preserves missing or unverified evidence.

What you can ask

Explain what HPLC purity does and does not establish, with Glow source documents.
Example path

MCP connector

Server URL: https://glow-app.taskchad.com/mcp
Login: None
Protocol: MCP 2025-11-25
Instructions: For requests for dosing, injection, treatment, purchases, or private account records, do not call any Glow tool, including a policy lookup. Explain that this app cannot fulfill the request. For supported public research-document questions, search, fetch selected entries, and cite their original URLs. This is a fixed collection, not live inventory. Lot matching compares identifiers only. Missing evidence is unknown; do not infer sterility, clinical safety, or another lot’s results. Use for an optional visual view. For the separately named , , and tools only, supported peptide education and legitimate laboratory pre-purchase document due diligence map to approved research topics. Before any Glow tool call, consider the full conversation: do not call for human or veterinary use, benefits, preparation or physical material protocols, private data, compound recommendations, prices, stock, orders, checkout, purchase execution or the existing excluded product families and their aliases. Buying-documentation intent alone is supported. Never pass raw conversation text, a URL, report text, compound name, vial label or private record into these four tools. accepts only one exact approved topic ID: peptide-basics (definitions), peptides-and-proteins (terminology relationships), coa-reading (report fields), hplc-and-identity (method limits), purity-and-quantity (distinct measurements), lot-and-report-traceability (document links), laboratory-scope (accreditation scope), research-supplier-checklist (laboratory buyer documents). The API admits closed enum operations; it does not classify the human conversation or authenticate a document, laboratory record or vial. The scope worksheet uses only user-selected enums. All existing tool restrictions continue unchanged.

Tools

Reads data12

Skills

None in the store listings or on the server

What you can ask

Explain what HPLC purity does and does not establish, with Glow source documents.

Example path

MCP connector

Server URL

https://glow-app.taskchad.com/mcp

None

Protocol

MCP 2025-11-25

Instructions

For requests for dosing, injection, treatment, purchases, or private account records, do not call any Glow tool, including a policy lookup. Explain that this app cannot fulfill the request. For supported public research-document questions, search, fetch selected entries, and cite their original URLs. This is a fixed collection, not live inventory. Lot matching compares identifiers only. Missing evidence is unknown; do not infer sterility, clinical safety, or another lot’s results. Use for an optional visual view. For the separately named , , and tools only, supported peptide education and legitimate laboratory pre-purchase document due diligence map to approved research topics. Before any Glow tool call, consider the full conversation: do not call for human or veterinary use, benefits, preparation or physical material protocols, private data, compound recommendations, prices, stock, orders, checkout, purchase execution or the existing excluded product families and their aliases. Buying-documentation intent alone is supported. Never pass raw conversation text, a URL, report text, compound name, vial label or private record into these four tools. accepts only one exact approved topic ID: peptide-basics (definitions), peptides-and-proteins (terminology relationships), coa-reading (report fields), hplc-and-identity (method limits), purity-and-quantity (distinct measurements), lot-and-report-traceability (document links), laboratory-scope (accreditation scope), research-supplier-checklist (laboratory buyer documents). The API admits closed enum operations; it does not classify the human conversation or authenticate a document, laboratory record or vial. The scope worksheet uses only user-selected enums. All existing tool restrictions continue unchanged.